Live / Aspire / Incident
Aspire: Aspire Experiencing Issue
Aspire · youraspire.comMajor incidentResolved2026-10-07 21:35 UTC
Public — what happened
Summary
Aspire reported a major incident on October 7, 2026, beginning at 15:28 UTC, in which some users had trouble getting into the Aspire service. About half an hour later, at 15:59 UTC, the company said the problem had been traced to one of its outside providers, which was working on a fix. Aspire said at 18:20 UTC that the provider's problem had been fixed and it was watching for any recurrence, and the incident was marked resolved at 21:35.
Affected
Aspire Core, Aspire Mobile
Timeline
- Started — 2026-10-07 15:28 UTC
- Investigating — 2026-10-07 15:28 UTC
- Identified — 2026-10-07 15:59 UTC
- Monitoring — 2026-10-07 18:20 UTC
- Resolved — 2026-10-07 21:35 UTC · 6h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Aspire against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Aspire: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Aspire report →
More from Aspire
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.