AT&T help and reporting
Use the provider’s help for AT&T wireless, internet and account servicing. Keep the failed step and its timestamp ready.
Live Domain Check
Run a live reachability check for att.com. Compare the regional responses with the problem you see in AT&T.
Find AT&T help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
For AT&T users in the United States, compare AT&T wireless, internet and account servicing with the public att.com website. A response from that hostname does not verify every signed-in account or app operation.
The checker above requests att.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual AT&T action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Other checks in connectivity & hosting: T-Mobile US status check, Verizon status check, Xfinity status check, Mint Mobile status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Use the provider’s help for AT&T wireless, internet and account servicing. Keep the failed step and its timestamp ready.
Open the website in your browser and compare it with the result above.
Open AT&T help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Country/product, affected devices, connection or account message and time; share line numbers and addresses only with official support.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to AT&T.
These are troubleshooting comparisons, not claims that AT&T is currently experiencing a particular incident.
Check whether ordinary browsing fails or only the AT&T account page; a billing-session failure is not evidence that the subscriber line is down.
Compare the subscriber service with account access, preferably using another available connection. Record device indicators before changing settings; a public website cannot test an individual line.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Check whether ordinary browsing fails or only the AT&T account page; a billing-session failure is not evidence that the subscriber line is down. Compare the subscriber service with account access, preferably using another available connection. Record device indicators before changing settings; a public website cannot test an individual line.
Use the community buttons on this page to share whether the service works for you. For help from AT&T, use the official help/reporting resource linked above. Use the provider’s help for AT&T wireless, internet and account servicing. Keep the failed step and its timestamp ready.
For AT&T users in the United States, compare AT&T wireless, internet and account servicing with the public att.com website. A response from that hostname does not verify every signed-in account or app operation. Compare the original measurement time with the specific action that failed.
Country/product, affected devices, connection or account message and time; share line numbers and addresses only with official support.