User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 29 min ago. Last stored result reached it in 65 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 62 ms | 0 |
| Tue 00 | 0 | 0.0 | 57 ms | 0 |
| Tue 02 | 0 | 0.0 | 122 ms | 0 |
| Tue 04 | 0 | 0.0 | 50 ms | 0 |
| Tue 06 | 0 | 0.0 | 34 ms | 0 |
| Tue 07 | 0 | 0.0 | 60 ms | 0 |
| Tue 09 | 0 | 0.0 | 59 ms | 0 |
| Tue 11 | 0 | 0.0 | 42 ms | 0 |
| Tue 13 | 0 | 0.0 | 74 ms | 0 |
| Tue 15 | 0 | 0.0 | 42 ms | 0 |
| Tue 17 | 0 | 0.0 | 130 ms | 0 |
| Tue 20 | 0 | 0.0 | 185 ms | 0 |
| Tue 22 | 0 | 0.0 | 71 ms | 0 |
| Wed 00 | 0 | 0.0 | 61 ms | 0 |
| Wed 02 | 0 | 0.0 | 45 ms | 0 |
| Wed 05 | 0 | 0.0 | 38 ms | 0 |
| Wed 07 | 0 | 0.0 | 71 ms | 0 |
| Wed 09 | 0 | 0.0 | 48 ms | 0 |
| Wed 11 | 0 | 0.0 | 36 ms | 0 |
| Wed 14 | 0 | 0.0 | 41 ms | 0 |
| Wed 16 | 0 | 0.0 | 108 ms | 0 |
| Wed 18 | 0 | 0.0 | 152 ms | 0 |
| Wed 20 | 0 | 0.0 | 201 ms | 0 |
| Wed 22 | 0 | 0.0 | 56 ms | 0 |
| Thu 01 | 0 | 0.0 | 76 ms | 0 |
| Thu 03 | 0 | 0.0 | 107 ms | 0 |
| Thu 05 | 0 | 0.0 | 55 ms | 0 |
| Thu 07 | 0 | 0.0 | 66 ms | 0 |
| Thu 09 | 0 | 0.0 | 89 ms | 0 |
| Thu 11 | 0 | 0.0 | 41 ms | 0 |
| Thu 13 | 0 | 0.0 | 32 ms | 0 |
| Thu 15 | 0 | 0.0 | 60 ms | 0 |
| Thu 17 | 0 | 0.0 | 61 ms | 0 |
| Thu 19 | 0 | 0.0 | 74 ms | 0 |
| Thu 21 | 0 | 0.0 | 356 ms | 0 |
| Thu 23 | 0 | 0.0 | 26 ms | 0 |
| Fri 01 | 0 | 0.0 | 41 ms | 0 |
| Fri 03 | 0 | 0.0 | 93 ms | 0 |
| Fri 05 | 0 | 0.0 | 40 ms | 0 |
| Fri 08 | 0 | 0.0 | 81 ms | 0 |
| Fri 10 | 0 | 0.0 | 67 ms | 0 |
| Fri 11 | 0 | 0.0 | 80 ms | 0 |
| Fri 13 | 0 | 0.0 | 59 ms | 0 |
| Fri 15 | 0 | 0.0 | 48 ms | 0 |
| Fri 17 | 0 | 0.0 | 52 ms | 0 |
| Fri 19 | 0 | 0.0 | 69 ms | 0 |
| Fri 20 | 0 | 0.0 | 116 ms | 0 |
| Fri 21 | 0 | 0.0 | 65 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Internal infrastructure upgrade
We will be undergoing maintenance to upgrade Port's backend to improve system stability and security. During this time Port's API in EU and US might be unavailable for all requests for a period of up to 15 minutes, we will update during the maintenance when this potential unavailability period starts. We will also update when the unavailability period ends and no further unavailability is…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Port yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Port goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Port alerts to Slack, Discord or a webhook — free.
Port, at port.io, is one of the AI services we monitor. The Agentic SDLC platform for building your own AI software factory that includes context, agent management and governance.
Port publishes an official status page at status.port.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 65 ms average, 26–116 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Port incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
65 ms on average over the last 24 hours (26–116 ms).
Yes, at https://status.port.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Port here at once, the problem is on Port's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Port. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.