Powered byCRASHPLAN

Questions? Call +31-157-112-149
or Contact us online

Destination status

NL-2718

ColoCenter Zoetermeer
PUE = 1.12

NL-5428

Commercial building
Green/eco-friendly hosting
Solar energy generator (77 kWp)
PUE = 1.03

D-40470

KPN international Düsseldorf

destination version GUID status

A. NL-2718 2010 332167474737380872 UP

B. NL-5428 2010 481346552014110214 UP

C. D-40470 2010 399883427204657979 UP

D. NL-2718 2010 399852153342589953 UP

E. NL-2718 3.x 534687437778648585 UP

F. NL-5428 3.x 569722707764357692 UP

G. D-40470 3.x 549052374817796921 UP

History

  • 14.11.17: B+F: no ip connection due to power outage in Culemborg due to helicopter crashing into high voltage power cables, downtime: 5 hours and 32 minutes
  • 12.11.17: B+F: new PDU, downtime 2-4 minutes per device
  • 13.10.17: A+D+E: new PDU, downtime 2-4 minutes per device
  • 08.10.17: A: fan replacement: downtime 5 minutes
  • 30.09.17: A+D+E: ip change, maximum dns change loss 1 hour 54 minutes
  • 30.09.17: D: PDU replacement, downtime 1 minute
  • 30.09.17: A+E: PDU replacement, downtime 3 minutes
  • 30.09.17: A+E: network link down, downtime 7 minutes
  • 28.09.17: B+F: network link down, downtime 9 minutes
  • 27.09.17: B: 23% of storage is having intermittent downtime, scheduled to be resolved in 3-7 days
  • 07.09.17: B: storage maintenance, downtime 11 minutes
  • 02.09.17: D: operating system freeze, downtime 16 hours 26 minutes, auto restart on freeze enabled
  • 30.08.17: B: unidentified disk failure, reboot, downtime 6 hours 30 minutes
  • 27.08.17: F: boot drive hardware failure, replaced, downtime 151 hours
  • 06.05.17: E: kernel panic zalloc: \"buf.8192\" (19507 elements) retry fail 3, kfree_nop_count: 0"@/SourceCache/xnu/xnu-1699.32.7/osfmk/kern/zalloc.c:1766, last loaded kext: com.apple.driver.AppleUSBCDC, downtime 8 hours 33 minutes
  • 17.02.17: E: drive maintenance, downtime 12 minutes
  • 18.01.17: C+G: unknown network provider issue, downtime 9 hours 26 minutes
  • 14.01.17: A+D+E: DDOS network attack, downtime 45 minutes
  • 01.01.17: B: controller replacement, downtime 11 minutes
  • 21.12.16: E: capacity expansion, downtime 2 minutes
  • 18.12.16: E: capacity expansion, downtime 10 minutes
  • 14.12.16: A+E: network provider down, downtime 13 minutes
  • 12.12.16: C+G: hardware move, downtime 22 hours
  • 25.10.16: E: unknown failure, downtime 83 hours
  • 23.10.16: F: spontaneous reboots + file system check, downtime 44 minutes
  • 21.10.16: B: boot disk failure, downtime: 47 hours
  • 06.10.16: B+F: power outage due to UPS overload, downtime 4 hours
  • 17.09.16: E: os crash, downtime 12 hours
  • 12.08.16: C+G: hardware returned, downtime (C) 54 hours (G) 13 days
  • 11.08.16: G: mainboard replaced with spare part, system restored from backup
  • 10.08.16: C+G: hardware retrieved from data center
  • 09.08.16: C+G: operating system crashes every approximately 5 minutes
  • 08.08.16: G: hard disk has been replaced; data has been copied
  • 05.08.16: G: according to tracking the shipment is still at the UPS Access Point™
  • 03.08.16: G: no issues found with the plain hard drive, ship back to Düsseldorf
  • 25.07.16: G: hard disk drive failure, data testing, expected downtime 21 days
  • 04.12.15: E: maintenance, downtime 7 minutes
  • 31.10.15: E: os kernel panic, memory issue or buffer overflow, downtime 10 hours
  • 22.10.15: B+F: fiber cable cut, downtime 28 hours
  • 15.08.15: E: storage controller fails, downtime 35 hours
  • 30.05.15: E: capacity expansion, unexpected downtime 48 minutes
  • 04.04.15: A: IP change, downtime 35 minutes
  • 09.03.15: E: OS crash that links back to HBA, downtime 2 days 10 hours
  • 04.11.14: F: defective hardware replace, downtime 4 hours
  • 04.11.14: E: software upgrade, downtime: 8 minutes
  • 31.10.14: B: capacity expansion, downtime: 15 minutes
  • 08.05.14: B: relocation, downtime: 2 hours
  • 23.04.14: A: router crashed and replaced, downtime 2 hours 20 minutes
  • 15.04.14: D: relocation, downtime 14 hours
  • 20.02.14: A: maintenance, downtime 8 minutes
  • 21.01.14: C: network outage, downtime 33 minutes
  • 17.01.14: A: maintenance, downtime 8 minutes
  • 08.08.13: A: capacity expansion, downtime 8 minutes
  • 30.07.13: A: crashplan server restart, downtime 7 minutes
  • 30.07.13: A: disk controller replaced, downtime 30 minutes
  • 29.07.13 A: crashplan software hang, downtime 6 minutes
  • 25.07.13 B: planned maintenance, downtime 1 hour
  • 13.07.13 A: emergency hardware relocation, downtime 8 hours
  • 14.06.13 A: crashplan software hang, downtime 19 minutes
  • 13.06.13 A: crashplan software hang, downtime 14 minutes
  • 12.06.13 A: crashplan software hang, downtime 14 minutes
  • 06.06.13 A: crashplan software hang, downtime 35 minutes
  • 30.05.13 A: crashplan software hang, downtime 23 minutes
  • 29.05.13 A: maintenance, downtime 35 minutes
  • 28.05.13 A: crashplan software hang, downtime 100 minutes
  • 26.05.13 A: crashplan software hang, downtime 18 minutes
  • 25.05.13 A: crashplan software hang, downtime 12 minutes
  • 24.05.13 A: storage replacement, downtime 20 minutes
  • 24.05.13 A: crashplan software hang, downtime 6 minutes
  • 23.05.13 A: crashplan software hang, downtime 29 minutes (21:46, 22:23, 22:56)
  • 19.05.13 A: unknown software error, downtime 11 hours 3 minutes
  • 16.05.13 A: unknown software error, downtime 7 minutes
  • 14.05.13 A: unknown software error, downtime 7 minutes
  • 02.05.13 A: hardware replacement, downtime 3 minutes
  • 12.04.13 A: hardware maintenance, downtime 7 minutes
  • 11.04.13 D: os updates and boot failure, downtime 1 hour 45 minutes
  • 09.04.13 A: hardware maintenance, downtime 9 minutes
  • 17.01.13 D: upstream network failure, downtime 15 hours
  • 17.01.13 B: os hung, downtime 11 hours
  • 31.12.12 A: storage expansion, downtime 24 minutes
  • 10.12.12 A: hardware maintenance, downtime 46 minutes
  • 27.11.12 B: file system failure, data migration, users affected: 50%
  • 27.11.12 B: file system, repaired incorrect block count, files affected: 31 of 5594
  • 26.11.12 B: file system, repaired incorrect block count, files affected: 90 of 5594
  • 20.11.12 A: file system failure, data migration, users affected: some
  • 30.10.12 D: network failure, downtime 1 hour
  • 29.10.12 A: storage replacement, downtime 8 minutes
  • 27.10.12 D: boot drive error repair, downtime 41 hours
  • 27.10.12 D: relocation to NL-2718, downtime 5 hours
  • 17.10.12 A: file system, repaired incorrect block count, files affected: 12 of 35880
  • 16.10.12 A: file system, repaired incorrect block count, files affected: 12 of 38999
  • 20.09.12 A: os update, downtime: 49 minutes
  • 16.09.12 C: startup drive capacity expansion, downtime: 9 minutes
  • 14.09.12 A: storage capacity expansion, downtime: 27 minutes
  • 07.09.12 C: boot failure, downtime: 11 hours 5 minutes
  • 22.08.12 A: replace failing storage, downtime: 15 minutes
  • 29.06.12 A: kernel crash and file system corruption, downtime: 12 minutes
  • 17.06.12 A: loose network cable, downtime: 3 hours 24 minutes
  • 19.05.12 A: hardware replacement, downtime: 7 minutes
  • 12.05.12 A: add watchdog hardware and os updates, downtime: 15 minutes
  • 08.04.12 A: partial storage failure (15%), data migration estimated time: 1 day
  • 06.03.12 A: human configuration error at upstream network provider; 10 minutes
  • 19.02.12 A: cable replacement; 21 minutes of downtime
  • 02.02.12 A: os update: less than 1 minute of downtime
  • 26.01.12 D: server reboot due (twice) for os updates: 16 minutes downtime
  • 22.01.12 D: server reboot due to os update: 10 minutes downtime
  • 13.01.12 A: router issues + fiber cable cut; 71 minutes down
  • 18.12.11 D: service crash, os patched and rebooted; 15 minutes down
  • 13.12.11 A: capacity expansion; 2 minutes downtime
  • 07.11.11 A: proserver was stopped and failed to start, reboot; 1 h 12 m down
  • 01.11.11 A: os update: 4 minutes downtime
  • 05.09.11 A: planned maintenance; 11 minutes downtime
  • 31.08.11 A: two storage mount points offline, relocated; 64 minutes down
  • 30.08.11 A: one storage mount point offline
  • 28.08.11 C: boot drive failure, replaced; 1 day 19 hours downtime
  • 23.08.11 A: os hang, updated; 2 hours 46 minutes down
  • 13.08.11 A: last customers migrated from drive containing failures
  • 12.08.11 A: kernel hang due to drive failure, 11 minutes down
  • 11.08.11 A: pre-failure indication of 3 drives, preventative taken out of order
  • 23.07.11 A: network router maintenance, to solve the frequent short network outages that occurred last three months, 25 minutes down
  • 22.07.11 D: server hangs, 14 minutes down
  • 21.07.11 D: server hang, 7 minutes down
  • 20.07.11 D: server hangs, 15 minutes down
  • 18.07.11 D: apc pdu failure, 48 minutes down
  • 16.07.11 C: storage down for capacity expansion, 5 hours down
  • 12.06.11 A: network ddos attack, 64 minutes of downtime
  • 02.06.11 D: bgp routing issues, 70 minutes of downtime
  • 25.05.11 A: maintenance, software upgrade, 3 minutes of downtime
  • 22.05.11 A: maintenance, pre failure data migration
  • 14.05.11 A: maintenance, restore data, capacity expansion, 59m down
  • 14.05.11 D: power feed lost, 138 minutes of downtime
  • 13.05.11 A: 1 more drive fail, replaced, 115 minutes of downtime
  • 12.05.11 A: 4 more drives fail, removed
  • 10.05.11 A: disk failure, replaced, 25 minutes of downtime
  • 09.05.11 A: storage failures, damaged cables, replaced, 58m down
  • 08.05.11 A: storage failure, disk and cable replaced, 42m down
  • 08.05.11 A: os hang, restarted, 2h 48m of downtime
  • 06.05.11 A: crashplan proserver software failure, restarted, 11m down
  • 04.05.11 A: storage failure, one out of seven volumes are out of order, data migration
  • 04.05.11 A: blocking storage failure, write-back write cache changed to write-through, 13 hours of downtime
  • 03.05.11 A: storage failure, two out of seven volumes are out of order
  • 03.05.11 D: os hang, restarted, 5h 5m of downtime
  • 02.05.11 A: psu Fortron FSP460-701UG failed, replaced with SuperMicro PWS-351-1H after 14 hours
  • 22.04.11 D: os hang, restarted, 2h 39m of downtime
  • 17.04.11 A: router problems, down during 35 minutes
  • 15.04.11 D: software updates, 51 minutes of downtime
  • 01.04.11 D: software updates, 13 minutes of downtime
  • 17.03.11 A: network packet loss / timeouts
  • 08.03.11 D: os hang, restarted, 10h 30m of downtime
  • 06.03.11 D: os reconfiguration, 22 minutes of downtime
  • 05.03.11 D: os reconfiguration, 7 minutes of downtime
  • 04.03.11 D: os hang, restarted, 8h 16m of downtime
  • 03.03.11 D: os hang, restarted, 47 minutes of downtime
  • 26.02.11 D: software updates, 4 minutes of downtime
  • 16.02.11 D: software updates, 6 minutes of downtime
  • 16.02.11 D: os hang, restarted, 3h 28m of downtime
  • 12.02.11 D: os hang, restarted, 12h 55m of downtime
  • 27.01.11 D: os hang, restarted, 9h 18m of downtime
  • 25.01.11 all: software upgrade, down during 5 till 11 minutes
  • 17.01.11 D: os hang, restarted, 7h 46m of downtime
  • 05.01.11 A: os hang (panic), unnecessary indexing process disabled + software update
  • 24.12.10 C: network DDoS attack, reduced connectivity
  • 13.12.10 C: network DDoS attack, reduced connectivity
  • 19.08.10 A: one harddisk finally fails, replaced
  • 18.08.10 A: intervention to move as much data as possible
  • 17.08.10 A: one disk generates errors, moving data
  • 13.08.10 A: one volume not mountable, replaced
  • 09.08.10 A: psu failure, replaced with spare #3
  • 08.08.10 A: psu failure, replaced with spare #2
  • 07.08.10 A: psu (Fortron FSP460-701UG) failed, replaced with spare #1
  • 06.08.10 A: all mount points offline, cause psu failure
  • 03.08.10 A: inbound speed was reduced from 1000 to 1Mbps, port limit removed
  • 25.07.10 A: connected to a different backbone switch, no downtime
  • 22.06.10 A: power lost, restored within 26 minutes
  • 27.05.10 C: massive packet loss during 15 minutes, router restarted and later replaced
  • 17.03.10 C: routing equipment partially down during 25 minutes
  • 13.03.10 C: equipment relocation, downtime < 1 hour
  • 01.07.09 A: start of service