Skip to content

Outage tracker / Go Module Proxy

Is Go Module Proxy down?

I'm having a problem

Checks passingchecked 6 minutes ago

Our checks of Go Module Proxy pass from all 10 regions we check.

As of Oct 22, 2026, 6:58 PM UTC, RealUptime's checks of Go Module Proxy passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Go Module Proxy did not fail from two or more distant regions in the 61 days we have checked it (since Aug 22, 2026). This does not show Go Module Proxy works for users.

our check readinglive · checked Oct 22, 2026, 6:58 PM UTC
US-East1397 msChecks passing
US-West645 msChecks passing
Europe906 msChecks passing
Asia-Pacific545 msChecks passing
US-Central278 msChecks passing
Canada243 msChecks passing
UK208 msChecks passing
Southeast Asia289 msChecks passing
Australia390 msChecks passing
South America228 msChecks passing
their status pagetheir claim, not our reading

Go Module Proxy publishes no status feed we can read, so the only reading here is our check reading on the left.

Go Module Proxy response time, by region

US-East
917msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 638ms2026-09-24 UTC: p95 907ms2026-09-25 UTC: p95 621ms2026-09-26 UTC: p95 645ms2026-09-27 UTC: p95 712ms2026-09-28 UTC: p95 554ms2026-09-29 UTC: p95 657ms2026-09-30 UTC: p95 693ms2026-10-01 UTC: p95 714ms2026-10-02 UTC: p95 418ms2026-10-03 UTC: p95 448ms2026-10-04 UTC: p95 485ms2026-10-05 UTC: p95 528ms2026-10-06 UTC: p95 462ms2026-10-07 UTC: p95 372ms2026-10-08 UTC: p95 469ms2026-10-09 UTC: p95 569ms2026-10-10 UTC: p95 361ms2026-10-11 UTC: p95 352ms2026-10-12 UTC: p95 374ms2026-10-13 UTC: p95 559ms2026-10-14 UTC: p95 633ms2026-10-15 UTC: p95 765ms2026-10-16 UTC: p95 648ms2026-10-17 UTC: p95 857ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 917ms
Sep 23Oct 7Oct 22
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 705ms2026-09-24 UTC: p95 663ms2026-09-25 UTC: p95 585ms2026-09-26 UTC: p95 684ms2026-09-27 UTC: p95 542ms2026-09-28 UTC: p95 650ms2026-09-29 UTC: p95 635ms2026-09-30 UTC: p95 529ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 442ms2026-10-03 UTC: p95 530ms2026-10-04 UTC: p95 806ms2026-10-05 UTC: p95 702ms2026-10-06 UTC: p95 450ms2026-10-07 UTC: p95 336ms2026-10-08 UTC: p95 276ms2026-10-09 UTC: p95 279ms2026-10-10 UTC: p95 277ms2026-10-11 UTC: p95 280ms2026-10-12 UTC: p95 667ms2026-10-13 UTC: p95 739ms2026-10-14 UTC: p95 703ms2026-10-15 UTC: p95 565ms2026-10-16 UTC: p95 482ms2026-10-17 UTC: p95 809ms2026-10-18 UTC: p95 970ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 803ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Europe
776msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 700ms2026-09-24 UTC: p95 695ms2026-09-25 UTC: p95 801ms2026-09-26 UTC: p95 707ms2026-09-27 UTC: p95 699ms2026-09-28 UTC: p95 758ms2026-09-29 UTC: p95 670ms2026-09-30 UTC: p95 604ms2026-10-01 UTC: p95 545ms2026-10-02 UTC: p95 550ms2026-10-03 UTC: p95 527ms2026-10-04 UTC: p95 471ms2026-10-05 UTC: p95 469ms2026-10-06 UTC: p95 530ms2026-10-07 UTC: p95 519ms2026-10-08 UTC: p95 337ms2026-10-09 UTC: p95 462ms2026-10-10 UTC: p95 522ms2026-10-11 UTC: p95 384ms2026-10-12 UTC: p95 455ms2026-10-13 UTC: p95 359ms2026-10-14 UTC: p95 321ms2026-10-15 UTC: p95 316ms2026-10-16 UTC: p95 374ms2026-10-17 UTC: p95 690ms2026-10-18 UTC: p95 856ms2026-10-19 UTC: p95 939ms2026-10-20 UTC: p95 626ms2026-10-21 UTC: p95 719ms2026-10-22 UTC: p95 776ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.8sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 938ms2026-10-04 UTC: p95 887ms2026-10-05 UTC: p95 933ms2026-10-06 UTC: p95 780ms2026-10-07 UTC: p95 782ms2026-10-08 UTC: p95 758ms2026-10-09 UTC: p95 825ms2026-10-10 UTC: p95 703ms2026-10-11 UTC: p95 716ms2026-10-12 UTC: p95 802ms2026-10-13 UTC: p95 848ms2026-10-14 UTC: p95 897ms2026-10-15 UTC: p95 950ms2026-10-16 UTC: p95 891ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 815ms2026-10-19 UTC: p95 832ms2026-10-20 UTC: p95 832ms2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
US-Central
654msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 582ms2026-09-24 UTC: p95 578ms2026-09-25 UTC: p95 516ms2026-09-26 UTC: p95 715ms2026-09-27 UTC: p95 649ms2026-09-28 UTC: p95 652ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 773ms2026-10-01 UTC: p95 593ms2026-10-02 UTC: p95 574ms2026-10-03 UTC: p95 614ms2026-10-04 UTC: p95 675ms2026-10-05 UTC: p95 452ms2026-10-06 UTC: p95 488ms2026-10-07 UTC: p95 406ms2026-10-08 UTC: p95 421ms2026-10-09 UTC: p95 513ms2026-10-10 UTC: p95 402ms2026-10-11 UTC: p95 458ms2026-10-12 UTC: p95 404ms2026-10-13 UTC: p95 587ms2026-10-14 UTC: p95 409ms2026-10-15 UTC: p95 487ms2026-10-16 UTC: p95 465ms2026-10-17 UTC: p95 412ms2026-10-18 UTC: p95 504ms2026-10-19 UTC: p95 616ms2026-10-20 UTC: p95 599ms2026-10-21 UTC: p95 637ms2026-10-22 UTC: p95 654ms
Sep 23Oct 7Oct 22
Canada
644msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 609ms2026-09-24 UTC: p95 578ms2026-09-25 UTC: p95 613ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 525ms2026-09-28 UTC: p95 481ms2026-09-29 UTC: p95 545ms2026-09-30 UTC: p95 560ms2026-10-01 UTC: p95 508ms2026-10-02 UTC: p95 523ms2026-10-03 UTC: p95 731ms2026-10-04 UTC: p95 684ms2026-10-05 UTC: p95 628ms2026-10-06 UTC: p95 556ms2026-10-07 UTC: p95 580ms2026-10-08 UTC: p95 632ms2026-10-09 UTC: p95 610ms2026-10-10 UTC: p95 644ms2026-10-11 UTC: p95 584ms2026-10-12 UTC: p95 521ms2026-10-13 UTC: p95 594ms2026-10-14 UTC: p95 573ms2026-10-15 UTC: p95 663ms2026-10-16 UTC: p95 633ms2026-10-17 UTC: p95 555ms2026-10-18 UTC: p95 630ms2026-10-19 UTC: p95 683ms2026-10-20 UTC: p95 734ms2026-10-21 UTC: p95 713ms2026-10-22 UTC: p95 644ms
Sep 23Oct 7Oct 22
UK
541msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 167ms2026-09-24 UTC: p95 176ms2026-09-25 UTC: p95 159ms2026-09-26 UTC: p95 208ms2026-09-27 UTC: p95 231ms2026-09-28 UTC: p95 285ms2026-09-29 UTC: p95 254ms2026-09-30 UTC: p95 162ms2026-10-01 UTC: p95 149ms2026-10-02 UTC: p95 131ms2026-10-03 UTC: p95 128ms2026-10-04 UTC: p95 117ms2026-10-05 UTC: p95 121ms2026-10-06 UTC: p95 130ms2026-10-07 UTC: p95 121ms2026-10-08 UTC: p95 119ms2026-10-09 UTC: p95 307ms2026-10-10 UTC: p95 114ms2026-10-11 UTC: p95 105ms2026-10-12 UTC: p95 160ms2026-10-13 UTC: p95 484ms2026-10-14 UTC: p95 117ms2026-10-15 UTC: p95 167ms2026-10-16 UTC: p95 351ms2026-10-17 UTC: p95 376ms2026-10-18 UTC: p95 363ms2026-10-19 UTC: p95 401ms2026-10-20 UTC: p95 236ms2026-10-21 UTC: p95 250ms2026-10-22 UTC: p95 541ms
Sep 23Oct 7Oct 22
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 915ms2026-09-25 UTC: p95 930ms2026-09-26 UTC: p95 897ms2026-09-27 UTC: p95 894ms2026-09-28 UTC: p95 812ms2026-09-29 UTC: p95 865ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 933ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 958ms2026-10-08 UTC: p95 905ms2026-10-09 UTC: p95 919ms2026-10-10 UTC: p95 922ms2026-10-11 UTC: p95 927ms2026-10-12 UTC: p95 932ms2026-10-13 UTC: p95 942ms2026-10-14 UTC: p95 922ms2026-10-15 UTC: p95 899ms2026-10-16 UTC: p95 919ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Australia
553msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 690ms2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 748ms2026-10-12 UTC: p95 979ms2026-10-13 UTC: p95 656ms2026-10-14 UTC: p95 697ms2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 645ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 841ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 601ms2026-10-22 UTC: p95 553ms
Sep 23Oct 7Oct 22
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22

Check your own site while you wait on Go Module Proxy

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Go Module Proxy. It cannot diagnose Go Module Proxy's own systems.

What we measured, function by function

Go Module Proxy answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Go Module Proxy fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Go Module Proxy fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Go Module Proxy's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1397msstatus code: 200checked: Oct 22, 2026, 6:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Go Module Proxy normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 645msstatus code: 200checked: Oct 22, 2026, 6:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Go Module Proxy normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 278msstatus code: 200checked: Oct 22, 2026, 6:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Go Module Proxy normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 243msstatus code: 200checked: Oct 22, 2026, 6:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Go Module Proxy normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 228msstatus code: 200checked: Oct 22, 2026, 6:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Go Module Proxy normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 906msstatus code: 200checked: Oct 22, 2026, 6:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Go Module Proxy normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 208msstatus code: 200checked: Oct 22, 2026, 6:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Go Module Proxy normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 545msstatus code: 200checked: Oct 22, 2026, 6:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Go Module Proxy normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 289msstatus code: 200checked: Oct 22, 2026, 6:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Go Module Proxy normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 390msstatus code: 200checked: Oct 22, 2026, 6:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Go Module Proxy normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Go Module Proxy, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Go Module Proxy yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Go Module Proxy.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Go Module Proxy since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Go Module Proxy covering any window you pick, with our check readings and Go Module Proxy's own claim at the time, side by side.

Full check history for Go Module Proxy: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Go Module Proxy uptime by RealUptime's checksLive, from this page's own readings.
[![Go Module Proxy uptime by RealUptime's checks](https://realuptime.io/outages/go-proxy/badge.svg?days=30)](https://realuptime.io/outages/go-proxy)
<a href="https://realuptime.io/outages/go-proxy"><img src="https://realuptime.io/outages/go-proxy/badge.svg?days=30" alt="Go Module Proxy uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Go Module Proxy down?", https://realuptime.io/outages/go-proxy. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Go Module Proxy's stated SLA

At or above your target

Our checks of Go Module Proxy failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Go Module Proxy's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://proxy.golang.org/golang.org/x/text/@v/list

What our check can and cannot see

A pass means the service returned real data from its own backend, with the content we expect. It does not show that every feature, account type or region works, or that sign-in is healthy.

Host checked: proxy.golang.org

RealUptime is not affiliated with Go Module Proxy; the name identifies what we checked, and nothing here speaks for Go Module Proxy's own team. We send a single web request to Go Module Proxy from 10 regions on our own schedule and time the response. We do not see inside Go Module Proxy's systems, do not use an account or real transaction, and are not the same signal Go Module Proxy's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Go Module Proxy is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.