User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fortawesome.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests fortawesome.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 441 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 428 ms | 0 |
| 03:15 | 0 | 0.0 | 158 ms | 0 |
| 03:30 | 0 | 0.0 | 182 ms | 0 |
| 03:45 | 0 | 0.0 | 535 ms | 0 |
| 04:00 | 0 | 0.0 | 236 ms | 0 |
| 04:15 | 0 | 0.0 | 425 ms | 0 |
| 04:30 | 0 | 0.0 | 227 ms | 0 |
| 04:45 | 0 | 0.0 | 192 ms | 0 |
| 05:00 | 0 | 0.0 | 433 ms | 0 |
| 05:15 | 0 | 0.0 | 592 ms | 0 |
| 05:30 | 0 | 0.0 | 590 ms | 0 |
| 05:45 | 0 | 0.0 | 106 ms | 0 |
| 06:00 | 0 | 0.0 | 757 ms | 0 |
| 06:15 | 0 | 0.0 | 691 ms | 0 |
| 06:30 | 0 | 0.0 | 80 ms | 0 |
| 06:45 | 0 | 0.0 | 592 ms | 0 |
| 07:00 | 0 | 0.0 | 502 ms | 0 |
| 07:15 | 0 | 0.0 | 493 ms | 0 |
| 07:30 | 0 | 0.0 | 278 ms | 0 |
| 07:45 | 0 | 0.0 | 441 ms | 0 |
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.
No outages on record for Font Awesome yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Font Awesome goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Font Awesome alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Font Awesome is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Font Awesome's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.