User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
gpters.org · AI
Is GPTers down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → gpters.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 21 min ago. Last stored result reached it in 932 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 836 ms | 0 |
| Mon 17 | 0 | 0.0 | 736 ms | 0 |
| Mon 20 | 0 | 0.0 | 880 ms | 0 |
| Mon 22 | 0 | 0.0 | 735 ms | 0 |
| Tue 00 | 0 | 0.0 | 785 ms | 0 |
| Tue 02 | 0 | 0.0 | 612 ms | 0 |
| Tue 04 | 0 | 0.0 | 640 ms | 0 |
| Tue 06 | 0 | 0.0 | 772 ms | 0 |
| Tue 08 | 0 | 0.0 | 706 ms | 0 |
| Tue 10 | 0 | 0.0 | 707 ms | 0 |
| Tue 12 | 0 | 0.0 | 890 ms | 0 |
| Tue 15 | 0 | 0.0 | 776 ms | 0 |
| Tue 17 | 0 | 0.0 | 765 ms | 0 |
| Tue 19 | 0 | 0.0 | 743 ms | 0 |
| Tue 21 | 0 | 0.0 | 708 ms | 0 |
| Wed 00 | 0 | 0.0 | 960 ms | 0 |
| Wed 02 | 0 | 0.0 | 737 ms | 0 |
| Wed 04 | 0 | 0.0 | 906 ms | 0 |
| Wed 06 | 0 | 0.0 | 640 ms | 0 |
| Wed 09 | 0 | 0.0 | 521 ms | 0 |
| Wed 11 | 0 | 0.0 | 616 ms | 0 |
| Wed 13 | 0 | 0.0 | 603 ms | 0 |
| Wed 15 | 0 | 0.0 | 803 ms | 0 |
| Wed 17 | 0 | 0.0 | 1005 ms | 0 |
| Wed 20 | 0 | 0.0 | 513 ms | 0 |
| Wed 22 | 0 | 0.0 | 754 ms | 0 |
| Thu 00 | 0 | 0.0 | 589 ms | 0 |
| Thu 02 | 0 | 0.0 | 589 ms | 0 |
| Thu 04 | 0 | 0.0 | 869 ms | 0 |
| Thu 06 | 0 | 0.0 | 617 ms | 0 |
| Thu 08 | 0 | 0.0 | 701 ms | 0 |
| Thu 10 | 0 | 0.0 | 728 ms | 0 |
| Thu 12 | 0 | 0.0 | 1069 ms | 0 |
| Thu 14 | 0 | 0.0 | 773 ms | 0 |
| Thu 16 | 0 | 0.0 | 566 ms | 0 |
| Thu 19 | 0 | 0.0 | 800 ms | 0 |
| Thu 21 | 0 | 0.0 | 1229 ms | 0 |
| Thu 23 | 0 | 0.0 | 666 ms | 0 |
| Fri 01 | 0 | 0.0 | 622 ms | 0 |
| Fri 03 | 0 | 0.0 | 625 ms | 0 |
| Fri 05 | 0 | 0.0 | 592 ms | 0 |
| Fri 07 | 0 | 0.0 | 657 ms | 0 |
| Fri 09 | 0 | 0.0 | 639 ms | 0 |
| Fri 11 | 0 | 0.0 | 737 ms | 0 |
| Fri 13 | 0 | 0.0 | 607 ms | 0 |
| Fri 15 | 0 | 0.0 | 563 ms | 0 |
| Fri 17 | 0 | 0.0 | 763 ms | 0 |
| Fri 19 | 0 | 0.0 | 932 ms | 0 |
Reliability
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.
Embed this status: free live GPTers badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for GPTers yet. Outages of 10 minutes or more get their own page here.
Having trouble with GPTers?
One report per service every 10 minutes from this network. No account.
Follow GPTers
Get an email when GPTers goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GPTers alerts to Slack, Discord or a webhook — free.
About GPTers
GPTers is listed in our AI category and checked at gpters.org. AI 최신 트렌드와 실전 활용 사례를 공유하는 GPTers 커뮤니티입니다. GPT를 넘어 바이브코딩과 생성형 AI까지, 다양한 AI 활용 경험을 나누고 함께 성장해요!
GPTers publishes an official status page at status.gpters.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 708 ms average, 563–1229 ms range across 14 successful checks.
Questions
Is GPTers down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was GPTers last down?
We have not recorded a public GPTers incident since monitoring began 7 days ago.
What is GPTers's uptime?
From our own checks: 100% over 7 days of checks.
How fast does GPTers respond?
708 ms on average over the last 24 hours (563–1229 ms).
Does GPTers have an official status page?
Yes, at https://status.gpters.org.
GPTers not working for me but the status is fine. What now?
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 GPTers here at once, the problem is on GPTers'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 GPTers. 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.