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.
The chart shows the latest five days of available recordings.
ICMP RTT / Milliseconds
Rolling five days · UTC
Enter time range
Bucket times use the selected timezone and include the UTC offset.
Choose a start and end in the displayed timezone.
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, tap, or use ← / → when the chart is focused to inspect a bucket. Drag across the chart to select a time range; on touch screens, first choose Select time range. Press Escape or choose Reset zoom to return. Hollow markers indicate partial intervals, incomplete samples or unknown coverage. The vertical scale adjusts to the selected endpoints and time range.
Select a point to inspect its average and sample coverage. Empty periods remain gaps.
Find the right connection for your building.
Check availabilityThe 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 25 seconds ago | Responding 27 seconds ago | Handshake verified 38 seconds ago | 1.274 | 1.274 msLast successful 7 seconds ago | 1.288 | 1.492 |
| 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 28 seconds ago | Responding 14 seconds ago | Handshake verified 51 seconds ago | 1.384 | 1.384 msLast successful 7 seconds ago | 1.473 | 1.903 |
| 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 26 seconds ago | Responding 0 seconds ago | Handshake verified 17 seconds ago | 6.445 | 6.445 msLast successful 7 seconds ago | 6.420 | 7.202 |
| 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 15 seconds ago | Responding 3 seconds ago | Handshake verified 11 seconds ago | 14.930 | 14.930 msLast successful 7 seconds ago | 16.733 | 18.499 |
| 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 12 seconds ago | Responding 14 seconds ago | Handshake verified 11 seconds ago | 0.882 | 0.882 msLast successful 7 seconds ago | 0.870 | 1.000 |
| 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 10 seconds ago | Responding 25 seconds ago | Handshake verified 2 seconds ago | 0.793 | 0.793 msLast successful 7 seconds ago | 0.784 | 0.864 |
| 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 14 seconds ago | Responding 21 seconds ago | Handshake verified 41 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 25 seconds ago | Responding 10 seconds ago | Handshake verified 51 seconds ago | 10.527 | 10.527 msLast successful 7 seconds ago | 18.042 | 28.843 |
| 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 23 seconds ago | Responding 25 seconds ago | Handshake verified 33 seconds ago | 0.219 | 0.219 msLast successful 7 seconds ago | 0.182 | 0.244 |
| 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 26 seconds ago | Responding 0 seconds ago | Handshake verified 16 seconds ago | 0.187 | 0.187 msLast successful 7 seconds ago | 0.183 | 0.249 |
| 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 14 seconds ago | Responding 1 seconds ago | Handshake verified 25 seconds ago | 1.161 | 1.161 msLast successful 7 seconds ago | 0.803 | 1.421 |
| 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 9 seconds ago | Responding 3 seconds ago | Handshake verified 50 seconds ago | 7.082 | 7.082 msLast successful 7 seconds ago | 7.107 | 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 24 seconds ago | Responding 27 seconds ago | Handshake verified 35 seconds ago | 0.781 | 0.781 msLast successful 7 seconds ago | 0.838 | 1.055 |
| 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 5 seconds ago | Responding 26 seconds ago | Handshake verified 18 seconds ago | 0.936 | 0.936 msLast successful 7 seconds ago | 0.856 | 1.409 |
| 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 25 seconds ago | Responding 25 seconds ago | Handshake verified 56 seconds ago | 0.776 | 0.776 msLast successful 7 seconds ago | 0.856 | 1.152 |
| 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 11 seconds ago | Not monitored | Not monitored | 0.527 | 0.527 msLast successful 7 seconds ago | 0.541 | 0.608 |
| 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 24 seconds ago | Responding 21 seconds ago | Handshake verified 37 seconds ago | 0.836 | 0.836 msLast successful 7 seconds ago | 0.877 | 1.028 |
| 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 25 seconds ago | Responding 26 seconds ago | Handshake verified 22 seconds ago | 1.081 | 1.081 msLast successful 7 seconds ago | 1.211 | 1.558 |
| 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 6 seconds ago | Responding 11 seconds ago | Handshake verified 45 seconds ago | 11.738 | 11.738 msLast successful 7 seconds ago | 11.161 | 55.168 |
| 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 18 seconds ago | Responding 1 seconds ago | Handshake verified 10 seconds ago | 6.558 | 6.558 msLast successful 7 seconds ago | 6.928 | 19.556 |
| 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 19 seconds ago | Responding 1 seconds ago | Handshake verified 38 seconds ago | 6.642 | 6.642 msLast successful 7 seconds ago | 2.270 | 6.450 |
| 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 10 seconds ago | Responding 27 seconds ago | Handshake verified 17 seconds ago | 6.991 | 6.991 msLast successful 7 seconds ago | 6.963 | 7.049 |
| 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 24 seconds ago | Responding 3 seconds ago | Handshake verified 39 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 12 seconds ago | Responding 17 seconds ago | Handshake verified 31 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 32 seconds ago | Responding 27 seconds ago | Handshake verified 40 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 26 seconds ago | Responding 26 seconds ago | Handshake verified 9 seconds ago | 1.478 | 1.478 msLast successful 7 seconds ago | 1.466 | 13.743 |
Measurement snapshot retrieved 09 Nov 2026 21:21:41 UTC. Observation window: 04 Nov 2026 21:21:41 to 09 Nov 2026 21:21:41 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.
Looking for resolvers? Explore our public DNS ping measurements.
- 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