Website down checker / porter.run
Is porter.run down right now?
ScaledPapers is not affiliated with Porter.
porter.run (Porter) is up and reachable from all 16 locations as of October 23, 2026 at 21:58 UTC (median response time 139 ms).
- Status
- Online
- Reachability
- 16 of 16 online
- Median response
- 139 ms
- Last checked
Probes this hostname from 16 locations.
Americas
Ashburn (us-east-1)
Online139ms
200 OK
Columbus (us-east-2)
Online111ms
200 OK
San Francisco (us-west-1)
Online120ms
200 OK
Portland (us-west-2)
Online140ms
200 OK
Montreal (ca-central-1)
Online134ms
200 OK
São Paulo (sa-east-1)
Online131ms
200 OK
Europe
Dublin (eu-west-1)
Online159ms
200 OK
London (eu-west-2)
Online133ms
200 OK
Paris (eu-west-3)
Online106ms
200 OK
Frankfurt (eu-central-1)
Online125ms
200 OK
Stockholm (eu-north-1)
Online142ms
200 OK
Asia Pacific
Tokyo (ap-northeast-1)
Online224ms
200 OK
Seoul (ap-northeast-2)
Online235ms
200 OK
Osaka (ap-northeast-3)
Online225ms
200 OK
Singapore (ap-southeast-1)
Online154ms
200 OK
Oceania
Sydney (ap-southeast-2)
Online130ms
200 OK
How to read a regional check
- All 16 regions failing
- The hostname is failing from every probe location. That usually means the origin is down, the TLS certificate has expired, or authoritative DNS is not answering. It is not a problem on one network path.
- One region or continent failing
- When a single city or one continent is offline and the rest return HTTP 200, the origin is up. The failure is usually a CDN or anycast edge route, or a regional cloud impairment between that probe and the site.
- All 16 regions return 200, but it fails in your browser
- The site is reachable from our probes. A local failure is usually a stale ISP DNS cache, a corporate firewall or VPN, or a browser extension blocking the request.
- HTTP 403 or 429 from the probes
- A 403 or 429 from many cloud probes often means a WAF or Cloudflare bot challenge is blocking AWS IP ranges. That is not the same as an application outage. Compare the status code with what your browser receives.
Need to know when something goes down?
Monitor any endpoint on a schedule and get Slack, Discord, PagerDuty, or webhook alerts. Free checks run every 5 minutes. Pro can check every 60 seconds.