User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
tiingo.com · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: @tiingo Staff Email unavailable due to Microsoft Outage
Source: the vendor's status page · We are not affiliated with Tiingo Inc.
Estimated fix: Not enough Tiingo Inc history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 290 ms.
Critical incident
@tiingo Staff Email unavailable due to Microsoft Outage Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 18:45 | 0 | 0.0 | 334 ms | 0 |
| 20:45 | 0 | 0.0 | 345 ms | 0 |
| 23:00 | 0 | 0.0 | 163 ms | 0 |
| 01:00 | 0 | 0.0 | 243 ms | 0 |
| 03:00 | 0 | 0.0 | 177 ms | 0 |
| 05:15 | 0 | 0.0 | 260 ms | 0 |
| 07:15 | 0 | 0.0 | 290 ms | 0 |
| 09:15 | 0 | 0.0 | 299 ms | 0 |
| 11:15 | 0 | 0.0 | 298 ms | 0 |
| 13:30 | 0 | 0.0 | 320 ms | 0 |
| 15:30 | 0 | 0.0 | 290 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tiingo Inc yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Tiingo Inc goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tiingo Inc alerts to Slack, Discord or a webhook — free.
Tiingo Inc, at tiingo.com, is one of the Cloud & developer services we monitor. A financial research platform dedicated to creating innovative financial tools for all, while adopting the motto, "Actively Do Good."
Tiingo Inc publishes an official status page at status.tiingo.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 266 ms average, 93–345 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: @tiingo Staff Email unavailable due to Microsoft Outage
We have not recorded a public Tiingo Inc incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
266 ms on average over the last 24 hours (93–345 ms).
Yes, at https://status.tiingo.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Tiingo Inc here at once, the problem is on Tiingo Inc's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Tiingo Inc. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.