Facebook bug reports surged across the United States on Friday morning, June 12, 2026, as users said they could not load Facebook, send messages in Messenger, or check their feeds. The disruption appeared to start around 10 a.m. Eastern time.
By 10:28 a.m. Eastern time, Meta had not issued a broad public explanation for the outage. Outage-tracking sites showed a sharp rise in reports during the morning, which suggests the problem spread fast enough to hit both daily scrolling and direct messaging at the same time.
Facebook and Messenger reports
The access problems hit Facebook and Messenger users across the United States. Some users also reported problems with Instagram. That wider reach turned a single-platform complaint into a broader Meta service failure for people trying to read updates, answer messages, or post at the start of the workday.
The practical effect was immediate for anyone relying on those apps for routine communication. Users who could not load a feed or send a message had no reliable workaround inside the apps themselves, so the outage forced them to wait rather than retry different settings.
10 a.m. Eastern time
The timing matters because the disruption appeared to begin around 10 a.m. Eastern time, and the report spike followed quickly. That pattern points to a fast-moving incident rather than isolated account trouble, especially since outage-tracking sites recorded a sharp increase in user complaints.
Large platform outages often clear without users changing account settings. That is why repeated password resets were discouraged unless Meta’s official channels prompted them, since resetting credentials during an access outage can create a second problem on top of the first.
Meta response window
The unresolved piece is Meta’s public response. By 10:28 a.m. Eastern time, there was still no broad explanation for what caused the outage or how long restoration would take.
