PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Go Module Proxy is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Go Module Proxy. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Go Module Proxy issues today?

As of Oct 12, 2026 20:17 UTC, 0 users had reported issues with Go Module Proxy in the previous 24 hours.

How can I report a Go Module Proxy outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Go Module Proxy down right now?

UnknownOfficial status last polled Sep 7, 2026 16:24 UTCproxy.golang.org Official status page

Go module proxy and checksum database availability for module downloads and dependency resolution.

Are you on the Go Module Proxy team and see something inaccurate? Report it to us. We respond within one business day.

Is Go Module Proxy down right now?

Unknown. Go Module Proxy does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 did not return a verifiable status page.

Status as of Oct 12, 2026 20:17 UTC

Unknown

Go Module Proxy: status unknown

As of Oct 12, 2026 20:17 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Aug 14, 2026 03:31 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Go Module Proxy.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Go Module Proxy. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Go Module Proxy outage on August 14 — 35-minute disruption

Aug 14, 02:56 AM → Aug 14, 03:31 AM · 35 minutes · high

On August 14, 2026, the Go Module Proxy experienced an outage that was detected via user reports. The incident began at 02:56 UTC and was fully resolved after 35 minutes, at 03:31 UTC.

Peak reports

in 15 min

Total reports

during the incident

Duration

35 minutes

tracked by PulseWatch

Impact

Users reported issues with the Go Module Proxy during the incident. A total of two reports were received, with a peak of eight reports within a 15-minute period. The primary issue type reported by users was related to security concerns. No specific regional impact was recorded during this time.

Top reported issues

Security issue2

Incident timeline

Aug 14, 02:56 AM
PulseWatch detected elevated report volume (high severity)
Aug 14, 03:00 AM
Peak of 2 reports in 15 minutes (baseline 1.3)
Aug 14, 03:31 AM
Report volume returned to baseline — incident resolved

Official updates

Aug 14, 02:56 AM
Go Module Proxy status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Go Module Proxy is unknown, so there is no incident history to measure and no uptime figure is shown.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Go Module Proxy incident correlated across 2 signal groups: synthetic probes, network health.

9/2/2026, 2:09:17 PM · 15 min

02:09 PM02:24 PM

Detection9/2/2026, 2:09:17 PM · 1mo ago

Detected — medium severity

Go Module Proxy incident correlated across 2 signal groups: synthetic probes, network health.

ResolvedMedium