Outages are filed under the Census area nearest the fault ESB reported. A cut that hit Tubbercurry may be listed under a neighbouring area, and one listed here may reach far beyond it - which is why a row can count more customers than Tubbercurry has people.
TubbercurryFault
121 customers affected · began Fri 6 Nov, 17:22 · restored 20:02 (2 h 40 min) · 13 min earlier than ESB estimated
TubbercurryFault
102 customers affected · began Sun 25 Oct, 02:19 · restored 13:45 (11 h 26 min) · 6 h 15 min earlier than ESB estimated
Outage began · 102 customers
25 customers still off
Supply restored
TubbercurryFault
66 customers affected · began Mon 19 Oct, 00:21 · restored 11:15 (10 h 54 min) · 1 h earlier than ESB estimated
TubbercurryFault
1,600 customers affected · began Mon 19 Oct, 00:11 · restored 07:53 (7 h 42 min) · 7 min earlier than ESB estimated
TubbercurryFault
66 customers affected · began Sun 18 Oct, 20:00 · off for about 30 min · no restore time published
TubbercurryFault
1,600 customers affected · began Sun 18 Oct, 19:08 · restored 23:41 (4 h 33 min) · 19 min earlier than ESB estimated
TubbercurryFault
243 customers affected · began Tue 11 Aug, 13:08 · restored 18:03 (4 h 55 min) · 2 h 3 min later than ESB estimated
Repeat fault - outage 2 of 2 at this location in quick succession
Outage began · 243 customers
10 customers still off
Supply restored
TubbercurryFault
498 customers affected · began Tue 11 Aug, 11:03 · off for about 2 h · no restore time published
Repeat fault - outage 1 of 2 at this location in quick succession
Outage began · 498 customers
61 customers still off
Last seen still out
TubbercurryFault
750 customers affected · began Thu 6 Aug, 17:51 · restored 18:12 (21 min) · 48 min earlier than ESB estimated
Outage began · 750 customers
489 customers still off
Supply restored
Nearby areas
The nearest areas with a page of their own - an outage close to the boundary may be filed under one of these.