Live / PEXA / Incident
PEXA: Service Issue - NT
PEXA · pexa.com.auMinor incidentResolved2026-10-08 04:38 UTC
Public — what happened
Summary
PEXA reported a minor issue affecting its services in the Northern Territory (NT), starting at 01:04 UTC on 8 October 2026, which could cause delays to Lodgement and Lodgement Verification. By 02:05 UTC the company said it had pinpointed the problem and stated that it did not originate on PEXA's side, though it did not describe the cause further. At 03:45 UTC PEXA said both functions were back to normal and began monitoring, and the incident was marked resolved at 04:38.
Affected
NT
Timeline
- Started — 2026-10-08 01:04 UTC
- Investigating — 2026-10-08 01:04 UTC
- Identified — 2026-10-08 02:05 UTC (2 updates)
- Monitoring — 2026-10-08 03:45 UTC
- Resolved — 2026-10-08 04:38 UTC · 3h 34m 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 42, 2026, our weekly internet health report.