All services / Travel

recreation.gov · Travel

Is Recreation.gov down?

Checks are succeeding and user reports are near the baseline.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → recreation.gov—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · 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, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 35 ms · 8 min ago.

Official status

No status feed

Recreation.gov does not publish a status feed we can read.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10683 ms23:3005:3011:3017:1523:15
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
18:4500.055 ms0
19:0000.0166 ms0
19:1500.051 ms0
19:3000.090 ms0
19:4500.017 ms0
20:0000.088 ms0
20:1500.0683 ms0
20:3000.0252 ms0
20:4500.034 ms0
21:0000.0645 ms0
21:1500.073 ms0
21:3000.0128 ms0
21:4500.0105 ms0
22:0000.038 ms0
22:1500.0312 ms0
22:3000.0239 ms0
22:4500.017 ms0
23:0000.042 ms0
23:1500.035 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Recreation.gov status badge Embed a live Recreation.gov status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Recreation.gov status and 30-day uptime badge

Past outages

No outages on record for Recreation.gov yet. Outages of 10 minutes or more get their own page here.

All Recreation.gov outages · Every recent outage

Having trouble with Recreation.gov?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

About Recreation.gov

We track Recreation.gov (recreation.gov) as part of the Travel group. Live checks and user reports.

Recreation.gov has no official status feed we can read, so this page relies on our own checks and user reports.

Common problems for travel services: booking and check-in failures, flight-status pages not loading, and app errors.

Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.

Response time over the last 24 hours: 179 ms average, 17–1221 ms range across 31 successful checks.

Questions

Is Recreation.gov down right now?

Checks are succeeding and user reports are near the baseline.

When was Recreation.gov last down?

We have not recorded a public Recreation.gov incident since monitoring began 1 day ago.

What is Recreation.gov's uptime?

From our own checks: 100% over 1 day of checks.

How fast does Recreation.gov respond?

179 ms on average over the last 24 hours (17–1221 ms).

Does Recreation.gov have an official status page?

Not one we can read. This page uses independent checks of recreation.gov and user reports.

Recreation.gov 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 travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report Recreation.gov here at once, the problem is on Recreation.gov's side.