What does reachable from NexIP mean?
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
← All services
Gaming
Is Steam down? Current status and outages
Доступен из точки NexIPHTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
Understanding the metrics
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Current state
Outage score
0/100
Statistical assessment
User signals
0
unique in the last 15 minutes
Automatic check
Available
Response: 723 ms
Response time
723 ms
Last local automatic check
User reports over the last 24 hours
Reports submitted to NexIP. One report does not prove a widespread outage.
Reports in selected period
0
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Recent incidents
No confirmed large-scale incidents were recorded during the last 7 days.
Observation points
Regional checks
Remote observation points are not connected yet.
Observation history
Latest automatic checks
OUTAGE INTELLIGENCE / SERVICE PROBES
Check history and reliability
Actual NexIP primary probe measurements, not user reports
Full-period overviewAll observations
Latest 40 intervals · CSV includes entire selection
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-12 19:00:00 | 7 | 783 ms | 939 ms | 0 | 0 |
| 2026-11-12 20:00:00 | 8 | 782 ms | 920 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 7 | 756 ms | 869 ms | 0 | 0 |
| 2026-11-12 22:00:00 | 8 | 694 ms | 750 ms | 0 | 0 |
| 2026-11-12 23:00:00 | 7 | 700 ms | 729 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 8 | 719 ms | 774 ms | 0 | 0 |
| 2026-11-13 01:00:00 | 7 | 758 ms | 1 094 ms | 0 | 0 |
| 2026-11-13 02:00:00 | 8 | 727 ms | 944 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 7 | 872 ms | 1 693 ms | 0 | 0 |
| 2026-11-13 04:00:00 | 8 | 720 ms | 852 ms | 0 | 0 |
| 2026-11-13 05:00:00 | 7 | 691 ms | 828 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 8 | 689 ms | 769 ms | 0 | 0 |
| 2026-11-13 07:00:00 | 7 | 710 ms | 802 ms | 0 | 0 |
| 2026-11-13 08:00:00 | 8 | 672 ms | 703 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 7 | 675 ms | 718 ms | 0 | 0 |
| 2026-11-13 10:00:00 | 8 | 679 ms | 741 ms | 0 | 0 |
| 2026-11-13 11:00:00 | 7 | 677 ms | 797 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 8 | 873 ms | 2 116 ms | 0 | 0 |
| 2026-11-13 13:00:00 | 7 | 675 ms | 703 ms | 0 | 0 |
| 2026-11-13 14:00:00 | 8 | 672 ms | 753 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 7 | 722 ms | 821 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 8 | 746 ms | 824 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 7 | 750 ms | 827 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 8 | 732 ms | 821 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 7 | 701 ms | 759 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 8 | 875 ms | 1 762 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 7 | 736 ms | 853 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 8 | 721 ms | 814 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 7 | 695 ms | 746 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 8 | 711 ms | 798 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 7 | 682 ms | 752 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 8 | 763 ms | 916 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 7 | 691 ms | 783 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 8 | 746 ms | 998 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 7 | 675 ms | 701 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 8 | 716 ms | 759 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 7 | 725 ms | 771 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 8 | 731 ms | 821 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 7 | 747 ms | 790 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 723 ms | 723 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
06:59
07:07
07:15
07:23
07:31
07:39
07:47
07:55
08:03
08:11
08:19
08:27
08:35
08:43
08:51
08:59
09:07
09:15
09:23
09:31
09:39
09:47
09:55
10:03
Last check
2026-11-14 10:03:04
HTTP
200
Response time
723 ms
Your signal
Having a problem with this service?
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
Community reviews
User opinions are separate from the technical outage status.
Your rating
No ratings yet
Leave a comment
Published comments
No comments yet.
Is Steam down?
This page tracks the current observed status of Steam, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is Steam down right now?
NexIP shows the current observed status of Steam using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Why can the service work for some users but not others?
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
How can I check whether the problem is on my side?
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.