Fastly's network points of presence in Johannesburg and Cape Town hit errors and increased latency for 2h 28m on 27 October 2026. Fastly's own status page confirms the fault sat on their side, in the African POPs, not in your configuration.
Started
15:46 UTC
Duration
Lasted 2h 28m
Source
IsDown
Next time
Fastly is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Africa, Cape Town (CPT), Johannesburg (JNB)
What happened?
Fastly logged one incident on 27 October 2026, starting at 15:46 UTC and running 2h 28m. The title Fastly gave it was "Cape Town (CPT), Johannesburg (JNB) with Possible Impact," covering errors and increased latency in the Johannesburg POP. Fastly's first update also noted that Cape Town had been affected earlier and separately, between 14:35 and 14:54 UTC, before recovering fully, so the day's record actually spans two windows of impact across the same two South African POPs. By 16:09 UTC Fastly said engineers had identified the contributing factor in Johannesburg and were building a fix, and stated plainly that all other products and services remained unaffected. At 17:28 UTC Fastly reported it was gradually returning traffic to the site, with some customers possibly still seeing intermittent issues as systems stabilised. No further update after that is on Fastly's page, and the incident is marked resolved with the 2h 28m duration. Fastly did not publish a cause for the contributing factor beyond saying it had been identified internally, so the underlying reason is not on the record. No user reports were filed during the window. Three components are listed as affected: Africa as a region, plus the Cape Town and Johannesburg POPs specifically.
Learning
UptimeRobot's own probes, which watch Fastly's api-control component from EU and North American regions, stayed at 100% uptime through this entire window, and that is not a contradiction. Those probes check a control-plane endpoint from outside Africa, while the actual fault sat inside the Johannesburg and Cape Town points of presence that serve traffic regionally. A regional POP problem can degrade requests routed through Africa without ever touching the control API that external monitors from other continents poll. This is the common shape of a CDN or edge-network outage: the edge serving your visitors in one region breaks while every global health check you'd normally rely on reports green. If your product serves African users through Fastly, your own uptime checks from elsewhere would have shown nothing wrong even as those users hit errors and latency. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.