Is facebook.com down?
Facebook appears to be a e-commerce website. StarNama monitors facebook.com for live uptime, response time, SSL status, server location, technology signals, and user reports so visitors can quickly understand whether the website is available or having access problems.
HTTP status completes first. Website information and validated SSL are refreshed in the following analysis phase.
Scores describe the observed technical signals. Response speed is measured from our server; it is not a browser loading or Core Web Vitals score.
facebook.com: Online
HTTP 200 · Response 201 ms
What the check found
No diagnostic result is available yet.
Check stage: http
Server & domain information
| Title | |
|---|---|
| Language | zh-Hans |
| CMS / platform | Shopify |
| Category | E-commerce Website |
| Server IP | 57.144.216.1 |
| Meta description | N/A |
| Robots.txt | Detected |
| Sitemap | Detected |
| Target server location | United States, Seattle |
| SSL status | Previous result: Valid (awaiting validation) · Expires: Tue, 20 Oct 2026 23:59:59 +0000 |
IP location can describe a CDN edge. It does not identify the check origin or prove where the website owner is based.
Performance & screenshot
Run a browser performance analysis or request a screenshot when you need it. Existing results are reused while fresh.
Not requested.
Not requested.
Website intelligence
Facebook appears to be a e-commerce website. StarNama monitors facebook.com for live uptime, response time, SSL status, server location, technology signals, and user reports so visitors can quickly understand whether the website is available or having access problems.
Visible homepage content: 9416 detected words. Last analysis: 2026-10-13 14:12:13
Detected technologies
Security headers
| strict-transport-security | max-age=15552000; preload |
|---|---|
| content-security-policy | default-src blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net *.facebook.net *.whatsapp.com *.whatsapp.net;script-src *.facebook.com *.fbcdn.net *.facebook.net 127.0.0.1:* 'nonce-YLviYA6l' blob: 'self' connect.facebook.net 'unsafe-eval' https://accounts.google.com https://*.google-analytics.com *.google.com;style-src *.fbcdn.net data: *.facebook.com 'unsafe-inline' https://accounts.google.com https://fonts.googleapis.com;connect-src *.facebook.com facebook.com *.fbcdn.net *.facebook.net wss://*.facebook.com:* wss://*.whatsapp.com:* wss://*.fbcdn.net attachment.fbsbx.com ws://localhost:* blob: *.cdninstagram.com 'self' http://localhost:3103 wss://gateway.facebook.com wss://edge-chat.facebook.com wss://snaptu-d.facebook.com wss://kaios-d.facebook.com/ v.whatsapp.net *.fbsbx.com *.fb.com *.instagram.com *.ipification.com https://accounts.google.com https://*.google-analytics.com;font-src data: *.facebook.com *.fbcdn.net *.fbsbx.com https://fonts.gstatic.com;img-src *.fbcdn.net *.facebook.com data: https://*.fbsbx.com facebook.com *.cdninstagram.com fbsbx.com fbcdn.net connect.facebook.net blob: android-webview-video-poster: *.whatsapp.net *.fb.com *.oculuscdn.com *.tenor.co *.tenor.com *.giphy.com https://trustly.one/ https://*.trustly.one/ https://paywithmybank.com/ https://*.paywithmybank.com/ https://www.googleadservices.com https://googleads.g.doubleclick.net https://*.google-analytics.com;media-src *.cdninstagram.com blob: *.fbcdn.net *.fbsbx.com www.facebook.com *.facebook.com data: *.tenor.co *.tenor.com https://*.giphy.com;child-src data: blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net;frame-src *.facebook.com *.fbsbx.com fbsbx.com data: www.instagram.com *.fbcdn.net accounts.meta.com *.accounts.meta.com *.fbthirdpartypixel.com *.ipification.com https://trustly.one/ https://*.trustly.one/ https://paywithmybank.com/ https://*.paywithmybank.com/ https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://td.doubleclick.net *.google.com *.doubleclick.net;manifest-src data: blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net;object-src data: blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net;worker-src blob: *.facebook.com data:;block-all-mixed-content;upgrade-insecure-requests; |
| x-frame-options | DENY |
| x-content-type-options | nosniff |
| referrer-policy | Not detected |
Detected technology and header values are public observations, not a security audit or malware verdict.
Technical signals & recommendations
Positive signals
- The last check reached a working HTTP response.
Recommended next steps
- Review the check stage, sample coverage and SSL details before drawing conclusions.
Report completeness: 100/100. This measures the evidence collected for this report.
Measured observations
facebook.com monitoring observations
The latest stored observation for facebook.com was recorded at 2026-11-04 04:35:56 UTC. Its observed status is UP, with HTTP result 200 and response time 201 ms. This is the result of the most recent probe from StarNama, rather than a guarantee that every visitor can access the website.
This report contains 194 retained historical checks. Of the 194 checks with a known availability result, 194 returned a successful HTTP response. The proportion of successful checks is 100 percent. This percentage describes collected samples; gaps between checks are not assumed to be monitored uptime.
Measured responses in the retained history average 190.03 ms across 194 samples. These server response measurements describe HTTP probe latency. Browser loading performance, rendering and Core Web Vitals require the separate performance analysis.
The observed website title is "Facebook". The stored page description is N/A. Detected technologies include Shopify, Cloudflare, Bootstrap, jQuery, React. Robots.txt was Detected; the sitemap was Detected. These observations can change when the target returns a maintenance page, redirects or restricts automated access.
Stored observations stay available while a requested refresh is waiting or running. An unavailable measurement does not mean that the website is offline. Access restrictions, DNS errors, TLS failures and server errors are reported separately when detected. Compare the check time, historical samples and diagnostic details with your own connection when investigating an access problem.
Historical checks
Successful checks: 100%
Samples: 194
Average response: 190 ms
The percentage is a share of successful observations, not guaranteed time-based uptime.
Recent samples, oldest to newest. Green: online · Red: offline · Amber: restricted / service issue · Gray: unknown.
Recent check details
| Checked at | Status | HTTP | Response |
|---|---|---|---|
| 2026-11-04 04:35:56 | UP | 200 | 201 ms |
| 2026-11-04 00:11:33 | UP | 200 | 227 ms |
| 2026-11-03 20:00:05 | UP | 200 | 304 ms |
| 2026-11-03 15:25:04 | UP | 200 | 284 ms |
| 2026-11-03 11:02:00 | UP | 200 | 193 ms |
| 2026-11-03 10:48:12 | UP | 200 | 200 ms |
| 2026-11-03 05:45:03 | UP | 200 | 165 ms |
| 2026-11-03 00:00:05 | UP | 200 | 209 ms |
| 2026-11-02 18:50:05 | UP | 200 | 394 ms |
| 2026-11-02 14:10:04 | UP | 200 | 546 ms |
| 2026-11-02 08:10:03 | UP | 200 | 493 ms |
| 2026-11-02 03:00:09 | UP | 200 | 660 ms |
| 2026-11-01 21:35:07 | UP | 200 | 720 ms |
| 2026-11-01 16:55:02 | UP | 200 | 456 ms |
| 2026-11-01 11:55:19 | UP | 200 | 328 ms |
| 2026-11-01 05:55:06 | UP | 200 | 302 ms |
| 2026-11-01 00:50:12 | UP | 200 | 463 ms |
| 2026-10-31 20:00:08 | UP | 200 | 596 ms |
| 2026-10-31 15:35:06 | UP | 200 | 324 ms |
| 2026-10-31 10:25:02 | UP | 200 | 352 ms |
Website change history
- 2026-10-13 02:01:14 ssl_expiry: Mon, 19 Oct 2026 23:59:59 +0000 → Tue, 20 Oct 2026 23:59:59 +0000
- 2026-10-12 01:10:04 ssl_expiry: Sun, 18 Oct 2026 23:59:59 +0000 → Mon, 19 Oct 2026 23:59:59 +0000
- 2026-10-11 07:52:44 ssl_expiry: Sat, 17 Oct 2026 23:59:59 +0000 → Sun, 18 Oct 2026 23:59:59 +0000
- 2026-10-10 03:21:03 ssl_expiry: Fri, 16 Oct 2026 23:59:59 +0000 → Sat, 17 Oct 2026 23:59:59 +0000
- 2026-10-09 05:50:01 ip: 57.144.104.1 → 57.144.216.1 ssl_expiry: Thu, 15 Oct 2026 23:59:59 +0000 → Fri, 16 Oct 2026 23:59:59 +0000
- 2026-10-07 21:05:59 ssl_expiry: Wed, 14 Oct 2026 23:59:59 +0000 → Thu, 15 Oct 2026 23:59:59 +0000
- 2026-10-06 20:01:06 ssl_expiry: Tue, 13 Oct 2026 23:59:59 +0000 → Wed, 14 Oct 2026 23:59:59 +0000
- 2026-10-06 15:26:02 ip: 57.144.216.1 → 57.144.104.1 ssl_expiry: Mon, 12 Oct 2026 23:59:59 +0000 → Tue, 13 Oct 2026 23:59:59 +0000
Community reports
0 issue reports today (UTC).
0 working · 0 not working
Community observations complement server checks. Repeated submissions are limited.
Public API & website badges
Embed the latest observed status, response time and technical health score.
Open SVG badge · Open HTML badge
The public API is disabled in StarNama settings. Status badges and widgets are available separately.
Claim this website
Prove domain control to add an official description. Verification supports a homepage meta tag, a verification file or DNS TXT record.
Compare & explore
Monitoring alerts
The StarNama Telegram bot supports status-change alerts for monitored domains.
Understand the evidence
One observation describes one moment from one monitoring location. More independent samples improve confidence.
When the site does not work for you
Compare the server check with your own connection. An online observation does not rule out regional, DNS, account or payment problems.
Local troubleshooting steps
- Try a hard refresh or a private browser window.
- Check another device and network to separate a local connection issue.
- Check DNS resolution and whether your device clock is correct for TLS.
- Report the specific problem above, including login or payment failures when the homepage still loads.
Windows DNS cache: ipconfig /flushdns. macOS DNS cache: sudo killall -HUP mDNSResponder.
FAQ
Is this site down now? Latest observation: Online.
Does it have a valid SSL certificate? Previous result: Valid (awaiting validation) · Expires: Tue, 20 Oct 2026 23:59:59 +0000
How do I check again? Use Check again; the stored report stays visible while the next check runs.