●Incident

SPTrans (São Paulo) outage.

ResolvedDEGRADATION · HIGH

Oct 11, 2026, 09:26 AM · 15 days ago · Duration: 6h 48min

Detected by Probecast

Incident Summary

Incident Summary

API SPTrans (São Paulo) is currently DOWN in us-west.

Diagnostic Details

Error Type: http HTTP Status: 503 Error Message: API returned HTTP 503 Retry Attempts: 1 (all failed)

Validation Results

Validation Reason: DOWN in 2 regions: europe, us-west Consecutive DOWN Checks: 2 Time Between Checks: 303s

Cross-Region Impact

Also DOWN in: europe Total Affected Regions: 2 Still UP in: us-east

Severity Assessment

Level: MEDIUM Limited regional impact or recoverable error type.


Detected by Probecast Health Monitor - 2026-10-11T09:26:31.673Z

Timeline

●Started

Oct 11, 2026, 09:26 AM

15 days ago

●Resolved

Oct 11, 2026, 04:15 PM

14 days ago

●Duration

6h 48min

Total downtime

Evidence Logs4 checks

TimeRegionStatusLatencyCode
Oct 11, 09:26 AMus-westdown183ms503
Oct 11, 09:21 AMeuropedown170ms503
Oct 11, 09:21 AMus-westdown183ms503
For the projects you ship

How many of your clients depend on SPTrans (São Paulo)?

When SPTrans (São Paulo) slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start freeBook 15 minutes →View SPTrans (São Paulo) full status →

Alerts land on email, Slack, push or webhooks — with the client's name on them.

Related Incidents