Your bandwidth.
All of it.
Dedicated capacity on infrastructure built and operated by Stealth. Plan bandwidth and interfaces around the work your business does.
Explore Dedicated InternetBusiness applications / Collaboration / Cloud servicesBusiness platforms.
Business platforms.
Connected.
Explore connectivity from Stealth’s New York City network to the public endpoints supporting everyday business applications, collaboration, and cloud services.
01 / The everyday connectionThe platforms
The platforms
behind your work.
A rolling five days of public endpoint observations. Separate views for ICMP round trip time, TCP connection establishment and TLS handshakes.
ICMP / Current checks22 / 264 no response · 0 unconfirmed · 0 monitoring unavailable
TCP / 443 / Current checks25 / 250 no response · 0 unconfirmed · 0 monitoring unavailable
TLS / Current checks25 / 250 no response · 0 unconfirmed · 0 monitoring unavailable
17 platforms · 26 public endpoints · 76 configured probes. Reachability checks describe individual protocols; they are not application availability scores.
Measurements available. The display refreshes every 60 seconds.
Collecting history. Public monitoring began 18 Oct 2026 16:26:27 UTC. There is not yet a full five days of history.
World time
Times at page load
-
San Francisco
20 OctUTC-07:00
-
New York
20 OctUTC-04:00
-
UTC
20 OctUTC+00:00
-
Moscow
20 OctUTC+03:00
-
Beijing
21 OctUTC+08:00
-
Tokyo
21 OctUTC+09:00
ICMP RTT / Milliseconds
Rolling five days · UTC
ICMP measures round trip time to the responding address. TCP and TLS views remain available when an endpoint does not answer ICMP.
Five minute arithmetic averages. Hover or focus the chart and use ← / → to inspect a bucket. Hollow markers indicate partial intervals, incomplete samples or unknown coverage.
Select a point to inspect its average and sample coverage. Empty periods remain gaps.
The latest observations.
ICMP RTT statistics use successful recordings. Current reachability comes from independent probe and scrape checks.
| Platform / Public endpoint | Service | ICMP | TCP / 443 | TLS | Current ICMP RTT | Last successful / UTC | Median | p95 |
|---|---|---|---|---|---|---|---|---|
| Adobe Creative Cloudassets.adobe.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Assets | Responding 80 seconds ago | Responding 74 seconds ago | Handshake verified 88 seconds ago | 1.365 | 1.365 msLast successful 83 seconds ago | 1.366 | 1.489 |
| Adobe Creative Cloudcreativecloud.adobe.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Creative Cloud | Responding 71 seconds ago | Responding 59 seconds ago | Handshake verified 105 seconds ago | 1.351 | 1.351 msLast successful 83 seconds ago | 1.378 | 1.506 |
| Amazon Web Servicess3.us-east-1.amazonaws.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | S3 Us East 1 | Responding 66 seconds ago | Responding 65 seconds ago | Handshake verified 79 seconds ago | 6.662 | 6.662 msLast successful 83 seconds ago | 6.410 | 7.182 |
| Amazon Web Servicess3.us-east-2.amazonaws.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | S3 Us East 2 | Responding 76 seconds ago | Responding 80 seconds ago | Handshake verified 108 seconds ago | 15.476 | 15.476 msLast successful 83 seconds ago | 16.882 | 18.522 |
| Atlassianapi.atlassian.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api Gateway | Responding 80 seconds ago | Responding 57 seconds ago | Handshake verified 84 seconds ago | 0.636 | 0.636 msLast successful 83 seconds ago | 0.581 | 0.897 |
| Boxapi.box.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 75 seconds ago | Responding 72 seconds ago | Handshake verified 113 seconds ago | 0.796 | 0.796 msLast successful 83 seconds ago | 0.780 | 0.828 |
| Cisco Webexwebexapis.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | No response 70 seconds ago | Responding 66 seconds ago | Handshake verified 57 seconds ago | — | — | — | — |
| Docusignaccount.docusign.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Authentication | Responding 61 seconds ago | Responding 86 seconds ago | Handshake verified 61 seconds ago | 11.028 | 11.028 msLast successful 83 seconds ago | 11.079 | 28.786 |
| Dropboxapi.dropboxapi.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 80 seconds ago | Responding 81 seconds ago | Handshake verified 107 seconds ago | 0.172 | 0.172 msLast successful 83 seconds ago | 0.230 | 0.560 |
| Dropboxcontent.dropboxapi.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Content | Responding 59 seconds ago | Responding 84 seconds ago | Handshake verified 108 seconds ago | 0.288 | 0.288 msLast successful 83 seconds ago | 0.218 | 0.531 |
| Figmaapi.figma.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 74 seconds ago | Responding 74 seconds ago | Handshake verified 111 seconds ago | 0.557 | 0.557 msLast successful 83 seconds ago | 0.571 | 1.322 |
| GitHubapi.github.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 58 seconds ago | Responding 81 seconds ago | Handshake verified 87 seconds ago | 6.686 | 6.686 msLast successful 83 seconds ago | 7.201 | 7.694 |
| Google Cloudstorage.googleapis.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Storage Api | Responding 60 seconds ago | Responding 85 seconds ago | Handshake verified 95 seconds ago | 6.554 | 6.554 msLast successful 83 seconds ago | 0.831 | 6.613 |
| Google Workspacedocs.google.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Docs | Responding 72 seconds ago | Responding 66 seconds ago | Handshake verified 58 seconds ago | 0.777 | 0.777 msLast successful 83 seconds ago | 0.854 | 0.977 |
| Google Workspacedrive.google.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Drive | Responding 76 seconds ago | Responding 63 seconds ago | Handshake verified 62 seconds ago | 0.828 | 0.828 msLast successful 83 seconds ago | 0.837 | 1.096 |
| Google Workspacelens.meet.l.google.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Meet Media | Responding 61 seconds ago | Not monitored | Not monitored | 0.510 | 0.510 msLast successful 83 seconds ago | 0.478 | 0.556 |
| Google Workspacemail.google.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Gmail | Responding 75 seconds ago | Responding 57 seconds ago | Handshake verified 91 seconds ago | 0.856 | 0.856 msLast successful 83 seconds ago | 0.835 | 6.445 |
| HubSpotapi.hubapi.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 71 seconds ago | Responding 71 seconds ago | Handshake verified 75 seconds ago | 9.765 | 9.765 msLast successful 83 seconds ago | 1.183 | 1.526 |
| Microsoft 365login.microsoftonline.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Identity | Responding 63 seconds ago | Responding 58 seconds ago | Handshake verified 106 seconds ago | 11.724 | 11.724 msLast successful 83 seconds ago | 11.163 | 55.053 |
| Microsoft 365outlook.office365.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Exchange | Responding 75 seconds ago | Responding 81 seconds ago | Handshake verified 83 seconds ago | 6.667 | 6.667 msLast successful 83 seconds ago | 6.901 | 20.822 |
| Microsoft 365teams.cloud.microsoftThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Teams Web | Responding 75 seconds ago | Responding 62 seconds ago | Handshake verified 66 seconds ago | 1.240 | 1.240 msLast successful 83 seconds ago | 2.261 | 6.556 |
| Microsoft Azuremanagement.azure.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Management Api | Responding 70 seconds ago | Responding 59 seconds ago | Handshake verified 84 seconds ago | 6.955 | 6.955 msLast successful 83 seconds ago | 6.578 | 7.131 |
| Salesforcelogin.salesforce.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Authentication | No response 87 seconds ago | Responding 80 seconds ago | Handshake verified 78 seconds ago | — | — | — | — |
| Slackwss-backup.slack.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Messaging Backup | No response 85 seconds ago | Responding 60 seconds ago | Handshake verified 72 seconds ago | — | — | — | — |
| Slackwss-primary.slack.comThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Messaging Primary | No response 81 seconds ago | Responding 81 seconds ago | Handshake verified 67 seconds ago | — | — | — | — |
| Zoomapi.zoom.usThis endpoint responds to TCP and TLS checks but did not answer ICMP. This pattern is consistent with ICMP filtering; these checks do not establish the cause. | Api | Responding 69 seconds ago | Responding 85 seconds ago | Handshake verified 99 seconds ago | 1.401 | 1.401 msLast successful 83 seconds ago | 1.450 | 15.644 |
Measurement snapshot retrieved 20 Oct 2026 17:53:30 UTC. Observation window: 15 Oct 2026 17:53:30 to 20 Oct 2026 17:53:30 UTC. A page refresh does not establish measurement freshness.
Explore chart data as a table
Browse the five-day window, including empty and partial buckets.
| Bucket / UTC | Average / ms | Successful samples | Coverage |
|---|---|---|---|
| Waiting for chart data. | |||
02 / Infrastructure for your businessA connection
A connection
you can build on.
Your bandwidth.
Connect your
cloud environments.
Explore private connections for your locations and cloud workloads. Confirm provider, region and connection options with our team.
Explore Cloud ConnectStart with
your address.
Find Stealth fiber in your building or discuss a new connection with our team.
Check availabilityThree checks.
A precise view.
Measurements originate from Stealth’s monitoring server at 32 Avenue of the Americas in NYC. Public hostnames may resolve to CDN or other shared service edges. These observations describe the responding public endpoints, rather than an application’s complete infrastructure.
- ICMP RTT
- Internet Control Message Protocol measures round trip time to the responding address. ICMP non-response alone does not establish an application outage.
- TCP probe duration
- Transmission Control Protocol checks connection reachability on port 443. The duration includes DNS resolution and TCP connection establishment.
- TLS probe duration
- Transport Layer Security checks connection establishment and the TLS handshake. Its duration includes DNS resolution, the TCP connection and the handshake.
TCP and TLS durations are separate measurements from ICMP RTT. Successful TCP or TLS checks do not establish that login, messaging, meetings, file transfers or other application workflows are functioning. These checks do not measure application response time.
The chart displays five minute arithmetic averages of successful recordings, in milliseconds, with no local baseline subtraction. Median is the middle successful value; p95 is the value at or below which 95% of successful values fall. Both statistics use underlying recordings for the same endpoint, protocol and available five-day window. They are not uptime or availability percentages.
Only samples inside the displayed five days are included. First and last intervals may be shorter than five minutes. Missing periods remain gaps. Hollow markers identify shorter intervals, fewer than the expected samples, or unknown coverage. A full bucket normally expects 10 ICMP, 10 TCP or 5 TLS recordings, based on the configured recording intervals.
Each protocol’s current status uses separate probe success and collection health checks. Samples older than two minutes are unconfirmed. A failed scrape or unavailable source is labeled “Monitoring unavailable”; a protocol intentionally not configured is “Not monitored.” An older successful measurement is labeled separately with its actual recording time and age.
If monitoring fails, retained observations are marked stale and limited to the current five days. Statistics are withheld until they can be recalculated from successful underlying recordings. No historical measurements are estimated.
Plan the connectionBuilt for
Built for
your work.
Tell us about your applications, locations and bandwidth requirements. We’ll help you plan the connection.
Discuss your connection