●Incident
TTC (Toronto) degradation.
ResolvedDEGRADATION · LOWOct 16, 2026, 04:05 PM · 2 days ago · Duration: 34min
Incident Summary
API has been degraded for 30 minutes in europe. Response times are consistently above normal thresholds.
Timeline
●Started
Oct 16, 2026, 04:05 PM
2 days ago
●Resolved
Oct 16, 2026, 04:40 PM
2 days ago
●Duration
34min
Total downtime
Evidence Logs20 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Oct 16, 04:05 PM | europe | degraded | 6775ms | 200 |
| Oct 16, 04:01 PM | us-east | degraded | 6602ms | 200 |
| Oct 16, 04:01 PM | us-west | degraded | 6706ms | 200 |
How many of your clients depend on TTC (Toronto)?
When TTC (Toronto) slows down, every client that depends on it feels it at once, and the first call usually goes to the agency. Probecast watches your clients' sites and the providers underneath them, shows which clients an outage touches, and turns the 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.
Alerts land on email, Slack, push or webhooks — with the client's name on them.