FCC (Federal Communications Commision outages and problems
User reports, last 24 hours
356 reports in total, counted in 15-minute windows
In the last hour, 298 problem reports came in for FCC (Federal Communications Commision, and at this time of day there are usually almost none. Over the last 24 hours there were 356 reports. Most recent reports were about forms & applications (100%). A spike in reports is going on now; it started 2 h ago. These are user reports from the US, where most people report FCC (Federal Communications Commision problems.
- NormalClose to the usual level22 h 15 min · 12 reports
- ElevatedMore than 1.5 times the usual level15 min · 10 reports
- OutageMore than twice the usual level and far above the day's average1 h 30 min · 334 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 356 user reports came in for FCC (Federal Communications Commision. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 93.75% uptime for the day.
The most recent spike big enough to count as an outage was under 15 minutes ago. The busiest 15-minute window of the day had 133 reports, in the last 15 minutes.
-
Outage
Ongoing, started 2 h agoRunning for 1 h 45 min133peak reports
FCC (Federal Communications Commision in November 2026
- Problem reports in November (since 13 November)
- 262
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for FCC (Federal Communications Commision.
Share of 1 recent report that said what was wrong.
FCC (Federal Communications Commision problem spikes, last 30 days
Since 13 November, FCC (Federal Communications Commision had 1 outage spike.
-
Outage
Fri 13 Nov, 23:10–00:55Still going143peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 13 November 2026. Monthly reports for all services
How to fix FCC (Federal Communications Commision not working
When FCC (Federal Communications Commision itself is having trouble, these steps won't bring it back, but they will rule out anything on your side:
Your browser tries to reach fcc.gov over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not FCC (Federal Communications Commision.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as FCC (Federal Communications Commision
Since 13 November, FCC (Federal Communications Commision's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
FCC (Federal Communications Commision: Fri 13 Nov, since 23:10
- Microsoft Teams, outage,12 Nov 15:41 to 14 Nov 00:55
- Microsoft Outlook, outage,12 Nov 17:42 to 14 Nov 00:55
- Microsoft 365, outage,12 Nov 17:59 to 14 Nov 00:55
- Microsoft OneDrive, outage,12 Nov 18:27 to 14 Nov 00:55
- Microsoft Copilot, outage,12 Nov 18:27 to 14 Nov 00:55
- Microsoft Store, outage,12 Nov 18:27 to 14 Nov 00:55
- Gmail, outage,12 Nov 18:38 to 14 Nov 00:55
- Microsoft Account, outage,12 Nov 18:38 to 23:37, 14 Nov 00:08 to 14 Nov 00:35
194 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
FCC (Federal Communications Commision IP address, servers and network
- IPv4 address
- 23.212.209.130
- IPv6 addresses
- 2a02:26f0:3500:2a8::132d
Show all 2
- 2a02:26f0:3500:2b2::132d
- Network
- AS16625 · Akamai Technologies, Inc., registered in the United States
- Served through
- Akamai
- DNS hosted by
- Akamai
- HTTPS certificate
- Issued by DigiCert Inc, valid until 21 Feb 2027 (99 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 33 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, less than an hour ago, for fcc.gov. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
11 of 12 locations got an answer from fcc.gov. 1 of the answers turned the automated check away (HTTP 403), which many sites do with bots; the site itself was up. Fastest from Los Angeles (39 ms), slowest from Paris (3,052 ms). Every location connected through Akamai Technologies, Inc. (AS16625), using 10 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 3,020 ms | 23.212.209.130 |
| ViennaAustria | Up · HTTP 301 | 1,024 ms | 23.209.23.141 |
| MilanItaly | Up · HTTP 301 | 2,064 ms | 23.212.209.130 |
| ParisFrance | Up · HTTP 301 | 3,052 ms | 23.59.64.126 |
| AmsterdamNetherlands | Up · HTTP 301 | 3,021 ms | 184.24.18.130 |
| MadridSpain | No result | – | – |
| WarsawPoland | Up · HTTP 301 | 1,017 ms | 104.81.111.125 |
| DallasUSA | Up · HTTP 301 | 1,019 ms | 104.90.23.130 |
| Los AngelesUSA | Up · HTTP 403 | 39 ms | 23.221.111.140 |
| São PauloBrazil | Up · HTTP 301 | 1,025 ms | 23.38.152.75 |
| SingaporeSingapore | Up · HTTP 301 | 3,048 ms | 23.14.194.129 |
| TokyoJapan | Up · HTTP 301 | 1,018 ms | 23.215.242.121 |
Checked with check-host.net from its servers in these cities less than an hour ago, for fcc.gov. Time is how long each server took to load the page.
Contact FCC (Federal Communications Commision support
Tip: FCC (Federal Communications Commision doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
Put the FCC (Federal Communications Commision status on your site
Paste one of these into a web page, a blog post or a README: a small badge, or a card with the chart. Both show the same status as this page, based on user problem reports, and link back here.
<a href="https://isitdownrightnow.app/services/fcc-federal-communications-commision/"><img src="https://isitdownrightnow.app/badge/fcc-federal-communications-commision.svg" alt="FCC (Federal Communications Commision status" height="20"></a>[](https://isitdownrightnow.app/services/fcc-federal-communications-commision/)A live card with the chart
The status, reports in the last hour and the last 24 hours, updated every 5 minutes. Use the frame, or the image where frames are not allowed, such as newsletters.
<iframe src="https://isitdownrightnow.app/embed/fcc-federal-communications-commision/" title="FCC (Federal Communications Commision status" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe>
<p><a href="https://isitdownrightnow.app/services/fcc-federal-communications-commision/">FCC (Federal Communications Commision status</a> from IsItDownRightNow.app</p><a href="https://isitdownrightnow.app/services/fcc-federal-communications-commision/"><img src="https://isitdownrightnow.app/share/fcc-federal-communications-commision.png" alt="FCC (Federal Communications Commision status: problem reports over the last 24 hours" width="600" height="315" loading="lazy"></a>[](https://isitdownrightnow.app/services/fcc-federal-communications-commision/)Badge, frame and image load no scripts from other sites and set no cookies; people who see them on your page load them from our server. More for journalists.
How we track FCC (Federal Communications Commision
The status on this page comes from user-submitted problem reports for FCC (Federal Communications Commision, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for FCC (Federal Communications Commision, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. FCC (Federal Communications Commision doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.