●Incident

TTC (Toronto) degradation.

ResolvedDEGRADATION · LOW

Nov 12, 2026, 12:34 PM · about 12 hours ago · Duration: 39min

Detected by Probecast

Incident Summary

API has been degraded for 30 minutes in us-west. Response times are consistently above normal thresholds.

Timeline

●Started

Nov 12, 2026, 12:34 PM

about 12 hours ago

●Resolved

Nov 12, 2026, 01:13 PM

about 12 hours ago

●Duration

39min

Total downtime

Evidence Logs20 checks

TimeRegionStatusLatencyCode
Nov 12, 12:34 PMus-westdegraded6188ms200
Nov 12, 12:32 PMeuropedegraded6608ms200
Nov 12, 12:30 PMus-eastdegraded6141ms200
For the projects you ship

How many of your clients depend on TTC (Toronto)?

When TTC (Toronto) 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 up to 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 TTC (Toronto) full status →

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

Related Incidents