onegetcdn.azureedge.net
🖥 Status: error
🕒 Response Time: 0.124 sec
⬅️ Response Code: 400
From April 7, 2024, forward over the next 278 days, there were 5 checks done on onegetcdn.azureedge.net's uptime. Every time onegetcdn.azureedge.net was checked as of January 11, 2025, it was reported as down or facing issues. Throughout the inspections carried out as of January 11, 2025, there were no cases of onegetcdn.azureedge.net being unavailable. The response from May 10, 2024, coded 400, was the latest error detected within the set of 5 error responses. According to the records, on May 10, 2024, onegetcdn.azureedge.net replied in a time of 0.124 seconds with an average response time of 0.235 seconds.
5
Last Updated: May 10, 2024
bettermarks.com
Last Updated: January 9, 2025
Status: up
Response Time: 0.199 sec
Response Code: 200
theinsidersnet.com
Last Updated: January 9, 2025
Status: up
Response Time: 0.373 sec
Response Code: 200
| Kazakhstan | 33.33% | ||||||||
| United States | 33.33% | ||||||||
| Russia | 33.33% | ||||||||
| 03:47 | 03:47 | 03:47 | |||||||
Search Results
| Site | Total Checks | Last Modified |
|---|---|---|
| 1 | September 9, 2024 | |
| 1 | January 11, 2025 | |
| 5 | April 7, 2024 | |
| 1 | January 11, 2025 | |
| 1 | January 11, 2025 |
Bettermarks.com | Onegetcdn.azureedge.net | ||||
|---|---|---|---|---|---|