by HonkWatch

Is TIM Italy down?

No. TIM Italy is working. Updated 4 Nov, 12:50 UTC, 2 min ago · No status page: this is what our own checks see Last problem: 4 Nov, 12:26 UTC, partial outage for 24 min (Could not be loaded from 12 of 34 cities).
Having trouble with TIM Italy?

Last 9030 days

Collecting since 4 Nov; the uptime figure shows after the first hour of readings

Of the last 90 days, 1 had a partial or major outage, 0 had maintenance only and 89 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of tim.it that failed (1,031 checks). Shaded: when our checks showed TIM Italy with a problem. We don't collect user reports.

0%27%54% 18:0000:0006:0012:00 38% of 130 checks failed34% of 140 checks failed53% of 173 checks failed49% of 152 checks failed33% of 138 checks failed54% of 177 checks failed50% of 121 checks failed

Our own checks of tim.it

Every 5 minutes, from our probes

12 of 34 cities can't reach tim.it.

Melbourne: loaded in 1154 ms Tel Aviv: loaded in 352 ms London: loaded in 125 ms Seattle: loaded in 664 ms Warsaw: loaded in 175 ms Dallas: loaded in 865 ms Portsmouth: loaded in 197 ms São Paulo: loaded in 880 ms Sydney: loaded in 2962 ms Doha: loaded in 528 ms Atlanta: loaded in 467 ms Los Angeles: loaded in 1030 ms New York: loaded in 561 ms Seoul: loaded in 1296 ms Amsterdam: loaded in 165 ms Hamina: loaded in 245 ms Frankfurt: loaded in 121 ms Madrid: loaded in 157 ms New Jersey: loaded in 528 ms Toronto: loaded in 582 ms Lauterbourg: loaded in 182 ms St. Louis: loaded in 696 ms Delhi: could not load it (RemoteDisconnected: Remote end closed connection without res) Jakarta: could not load it (RemoteDisconnected: Remote end closed connection without res) Hong Kong: could not load it (RemoteDisconnected: Remote end closed connection without res) Querétaro: could not load it (RemoteDisconnected: Remote end closed connection without res) Osaka: could not load it (RemoteDisconnected: Remote end closed connection without res) Bangalore: could not load it (RemoteDisconnected: Remote end closed connection without res) Tokyo: could not load it (RemoteDisconnected: Remote end closed connection without res) Singapore: could not load it (RemoteDisconnected: Remote end closed connection without res) Santiago: could not load it (RemoteDisconnected: Remote end closed connection without res) Johannesburg: could not load it (RemoteDisconnected: Remote end closed connection without res) Cape Town: could not load it (RemoteDisconnected: Remote end closed connection without res) Mumbai: could not load it (RemoteDisconnected: Remote end closed connection without res)
  • DelhiServer closed the connection526 ms, just now
  • JakartaServer closed the connection505 ms, just now
  • Hong KongServer closed the connection488 ms, just now
  • QuerétaroServer closed the connection310 ms, just now
  • OsakaServer closed the connection445 ms, just now
  • BangaloreServer closed the connection480 ms, just now
  • TokyoServer closed the connection465 ms, just now
  • SingaporeServer closed the connection309 ms, just now
  • SantiagoServer closed the connection470 ms, just now
  • JohannesburgServer closed the connection338 ms, just now
  • Cape TownServer closed the connection362 ms, just now
  • MumbaiServer closed the connection253 ms, just now
  • MelbourneReachable1154 ms, just now
  • Tel AvivReachable352 ms, just now
  • LondonReachable125 ms, just now
  • SeattleReachable664 ms, 1 min ago
  • WarsawReachable175 ms, 1 min ago
  • DallasReachable865 ms, 1 min ago
  • PortsmouthReachable197 ms, 1 min ago
  • São PauloReachable880 ms, 1 min ago
  • SydneyReachable2962 ms, 1 min ago
  • DohaReachable528 ms, 1 min ago
  • AtlantaReachable467 ms, 1 min ago
  • Los AngelesReachable1030 ms, 1 min ago
  • New YorkReachable561 ms, 1 min ago
  • SeoulReachable1296 ms, 1 min ago
  • AmsterdamReachable165 ms, 1 min ago
  • HaminaReachable245 ms, 1 min ago
  • FrankfurtReachable121 ms, 1 min ago
  • MadridReachable157 ms, 1 min ago
  • New JerseyReachable528 ms, 1 min ago
  • TorontoReachable582 ms, 1 min ago
  • LauterbourgReachable182 ms, 1 min ago
  • St. LouisReachable696 ms, 1 min ago

We load tim.it the way a visitor would and note whether it answers.

No status page

TIM Italy does not publish a status page, so there is nothing for us to read. What you see here is what we measure ourselves: its website is loaded from our probes in 34 cities every 5 minutes. We show a problem when a quarter of the cities that are working normally can't load it, and an outage when half can't. A city that has not been able to load it once in the last two days is left out: some sites only open for people in their own country, and that is not an outage. When too few cities are left, we say we can't tell.

Recent problems

4 Nov, 12:26 UTCPartial outage24 minCould not be loaded from 12 of 34 cities
4 Nov, 12:10 UTCPartial outage8 minCould not be loaded from 12 of 34 cities

Alert me when TIM Italy is down

HonkWatch can load TIM Italy's website for you from several cities and alert you by email, Slack, Discord or Telegram when it stops answering.

Start free Log in

More in Telecom and internet

Questions

Is TIM Italy down, or is it just me?

Our checks reach TIM Italy's website from most of our cities. If it isn't working for you, the cause is more likely near you: your network, your browser, or a problem only in your area. Try another network or device.

How do we know?

TIM Italy has no public status page. We load tim.it from our own probes in several cities and note whether it answers. We don't guess from social media posts or reports.

How often do we check?

The website every 5 minutes, day and night. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Our own checks of the TIM Italy website. HonkWatch also checks websites from 34 cities.

← All services