GWI Outage History
10 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded GWI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 10, 2026 | Service degradationThis incident has been resolved. Spark API requests and API token creation are operating normally. The cause was an internal service compatibility issue, which has been fixed. | 1h 30m | Resolved |
| Aug 17, 2026 | Service degradationThis incident is now resolved. The issue causing garbled/illegible characters on app.globalwebindex.com was due to stale assets served from cache; If you experience any further issues, please contact support. | 3h 12m | Resolved |
| Aug 13, 2026 | Availability Issues on APAC RegionThe issue has been resolved, and our services are now available again in the APAC region. | 29 min | Resolved |
| Jul 16, 2026 | Authentication issues affecting MCP integrationsThe affected features are now fully available. | 1h 9m | Resolved |
| Apr 5, 2026 | Scheduled resilence testThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 10, 2026 | Limited access issues for select US usersA client who was impacted by this issue has confirmed that it has now been resolved. | 9h 12m | Resolved |
| Dec 5, 2025 | Service degradationThe root cause of the issue has been eliminated and your systems are back to 100% performance. | 2h 27m | Resolved |
| Nov 27, 2025 | Service degradationThis incident is now considered fully resolved. All systems are functioning normally, and we have observed sustained stability following the fix. | 30 min | Resolved |
| Nov 14, 2025 | Service degradationEverything has been stable for the last hours, so we’re closing out the monitoring phase. Systems continue to look healthy. | 4h 34m | Resolved |
| Nov 13, 2025 | Service degradationService login functionality has been restored. Systems are operating normally. Continuing to monitor for recurrence. | 1h 9m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next GWI incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This GWI Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GWI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single GWI outage in this window ran 9h 12m, against a mean recovery of 2h 31m. If you depend on GWI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.