Live / PEXA / Incident
PEXA: Service Issue - TAS
PEXA · pexa.com.auMinor incidentResolved2026-10-13 05:13 UTC
Public — what happened
Summary
PEXA reported a minor issue affecting its services in Tasmania (TAS) starting at 01:04 UTC on 12 October 2026, initially warning of possible delays to Lodgement Verification and soon after to Lodgement as well. The company stated the problem did not originate on PEXA's side, and at 06:24 UTC that day it said both functions were back to normal, though a backlog of pending lodgements would take time to clear. The delays returned at 22:46 UTC on 12 October, and PEXA said services were working normally again by 02:06 UTC on 13 October, again describing the issue as outside its own systems. The incident was marked resolved at 05:13 on 13 October.
Affected
TAS
Timeline
- Started — 2026-10-12 01:04 UTC
- Investigating — 2026-10-12 01:04 UTC (5 updates)
- Identified — 2026-10-12 05:27 UTC
- Monitoring — 2026-10-12 06:24 UTC
- Investigating — 2026-10-12 22:46 UTC (3 updates)
- Monitoring — 2026-10-13 02:06 UTC (3 updates)
- Resolved — 2026-10-13 05:13 UTC · 28h 08m 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 PEXA 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 PEXA: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the PEXA report →
More from PEXA
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.