User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
getnet.net · 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 25 min ago. Last stored result reached it in 951 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 1256 ms | 0 |
| Nov 7 | 0 | 0.0 | 1428 ms | 0 |
| Nov 8 | 0 | 0.0 | 1164 ms | 0 |
| Nov 8 | 0 | 0.0 | 798 ms | 0 |
| Nov 8 | 0 | 0.0 | 1250 ms | 0 |
| Nov 8 | 0 | 0.0 | 1086 ms | 0 |
| Nov 9 | 0 | 0.0 | 1428 ms | 0 |
| Nov 9 | 0 | 0.0 | 1200 ms | 0 |
| Nov 9 | 0 | 0.0 | 1112 ms | 0 |
| Nov 9 | 0 | 0.0 | 1045 ms | 0 |
| Nov 10 | 0 | 0.0 | 1001 ms | 0 |
| Nov 10 | 0 | 0.0 | 1084 ms | 0 |
| Nov 10 | 0 | 0.0 | 1058 ms | 0 |
| Nov 10 | 0 | 0.0 | 1145 ms | 0 |
| Nov 11 | 0 | 0.0 | 1247 ms | 0 |
| Nov 11 | 0 | 0.0 | 982 ms | 0 |
| Nov 11 | 0 | 0.0 | 989 ms | 0 |
| Nov 11 | 0 | 0.0 | 1115 ms | 0 |
| Nov 12 | 0 | 0.0 | 1270 ms | 0 |
| Nov 12 | 0 | 0.0 | 1317 ms | 0 |
| Nov 12 | 0 | 0.0 | 1458 ms | 0 |
| Nov 12 | 0 | 0.0 | 1037 ms | 0 |
| Nov 13 | 0 | 0.0 | 1404 ms | 0 |
| Nov 13 | 0 | 0.0 | 1052 ms | 0 |
| Nov 13 | 0 | 0.0 | 951 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.
No outages on record for Getnet 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 Getnet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Getnet alerts to Slack, Discord or a webhook — free.
Getnet, at getnet.net, is one of the AI services we monitor. We are a leading AI payments company in Latin America and Iberia.
Getnet publishes an official status page at status.getnet.net; 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: 1132 ms average, 589–1653 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Getnet incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1132 ms on average over the last 24 hours (589–1653 ms).
Yes, at https://status.getnet.net.
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 Getnet here at once, the problem is on Getnet'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 Getnet. 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.