Wanted to follow up here. We received the below message from Meraki today. I verified that the search was working. With the working search, we could see that one of our internal domains is being flagged as "Advertisements", which we block. Yesterday, it wasn't showing a category in the Meraki "event log". It is now showing the "Advertisements" category on any domain or subdomain using that internal root domain. We do own the domain, so we are not sure how it was flagged as "Advertisement" as it's not used externally. Response from Meraki: Thank you for your patience as the engineering team has been able to work on providing a solution. I received word from the Engineering team that this issue has been resolved. ... View more

There is an Internet provider MX250 sitting in front of our MX68. I know that it blocks the inbound traffic, not for the Site-to-Site VPN ecnryption domain traffic of course. But I wonder how that device is doing that, since it is MX series as well. ... View more

We are getting this as well.   File Name / Hash: ArchiveFile / 975c0d48c41d2ad76a242d5f7270f4bf8063bb9c753b375ab2c47c9e2060f562 File URI   http://4.tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/3d3c4265-57fd-450e-9bda-9fb5f4612029?P1=1681143101&P2=404&P3=2&P4=bk3exk61txqkVyVVPmJVNGIygKC7X1OmJAgfnsJUPXJzgjaie7QobtBuyPDPIsFlVy4u0GWLbO4Czo6%2blArhAw%3d%3d Server IP 68.142.107.4 ... View more

Yep. It went completely retrospectively clean. It's a good day after all. ... View more

Following up... This file is now marked as "clean" for me and is no longer appearing in the dashboard alerts. I believe this has been "resolved" ... View more

Issue is resolved.   https://status.meraki.net/incidents/66pj1lx1m4vs ... View more

Issue is resolved.   https://status.meraki.net/incidents/66pj1lx1m4vs ... View more

that's a distribution node on Level3's backbone. They have endpoints all over, and are pretty much a tier 0 network ... View more