BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:TransPAC2 Unscheduled Outages
PRODID:-//Apple Computer, Inc//iCal 2.0//EN
X-WR-RELCALID:9F5CEEB3-53E1-4CDE-9E76-62-unsched_maint
X-WR-TIMEZONE:America/Indianapolis
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20060516T001701Z
SUMMARY:  543 TransPAC2 Peer APAN Outage Resolved
DTEND:20060516T003801Z
DESCRIPTION:TICKET NUMBER: 543\nOUTAGE TYPE: Software\nAFFECTED: TransPAC2 Peer APAN\n\nSTART TIME: Tuesday, May 16, 2006, 12:17 AM (0017)\nEND TIME: Tuesday, May 16, 2006, 12:38 AM (0038)\nDESCRIPTION:  TransPAC2 Peer APAN was unavailable to the TransPAC2 Community. APAN engineers report the outage was due to APAN-TW exceeding their maximum prefix limit.  New BGP peering configs have been applied.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=543&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20061006T175801Z
SUMMARY:  582 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20061006T180201Z
DESCRIPTION:TICKET NUMBER: 582\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 Peer APAN via TransPAC2\n\nSTART TIME: Friday, October 6, 2006, 5:58 PM (1758)\nEND TIME: Friday, October 6, 2006, 6:02 PM (1802)\nDESCRIPTION:  TransPAC2 Peer APAN via TransPAC2 was unavailable. APAN engineers reported that this was a scheduled maintenanace performed by circuit provider VSNL.  Maintenance was supposed to be non-service impacting.  However the technician accidently bumped the fiber.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=582&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20060526T212701Z
SUMMARY:  552 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage
DTEND:20060526T092701Z
DESCRIPTION:TICKET NUMBER: 552\nOUTAGE TYPE: Circuit---Other\nAFFECTED: S050403100 Transpac2 10G Tokyo-Los Angeles\n\n\nSTART TIME: Friday, May 26, 2006, 9:27 PM (2127)\nEND TIME: Friday, May 26, 2006, 9:27 AM (0927)\nDESCRIPTION:  Circuit outage
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=552&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20060615T234801Z
SUMMARY:  560 TransPAC2 Peers Abilene (STTL) And NLR
DTEND:20060616T054601Z
DESCRIPTION:TICKET NUMBER: 560\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: Peer Abilene STTL And NLR\n\nSTART TIME: Thursday, June 15, 2006, 11:48 PM (2348)\nEND TIME: Friday, June 16, 2006, 5:46 AM (0546)\nDESCRIPTION:  Peer Abilene STTL is unavailable due to a damaged Level (3) Fiber
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=560&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20060901T154601Z
SUMMARY:  574 TransPac2 Various Peers Outage
DTEND:20060902T004601Z
DESCRIPTION:TICKET NUMBER: 574\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: Peers Abilene, PNWGP, and NLR\n\nSTART TIME: Friday, September 1, 2006, 3:46 PM (1546)\nEND TIME: Saturday, September 2, 2006, 12:46 AM (0046)\nDESCRIPTION:  Transpac2 peering with Abilene, PNWGP, and NLR experienced an outage due to a fiber cut in Oakland, CA. The vendor repaired the fiber cut and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=574&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20060907T041701Z
SUMMARY:  577 TransPAC2 Peers NLR PacketNet and Abilene (STTL) Instability Resolved
DTEND:20060909T001001Z
DESCRIPTION:TICKET NUMBER: 577\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peer NLR PacketNet and Abilene (STTL)\n\nSTART TIME: Thursday, September 7, 2006, 4:17 AM (0417)\nEND TIME: Saturday, September 9, 2006, 12:10 AM (0010)\nDESCRIPTION:  TransPAC2 Peers NLR PacketNet and Abilene (STTL) became unstable to the community.  NLR L1 NOC Engineers worked with the vendor to resolve an APR issue and service was restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=577&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20061019T011901Z
SUMMARY:  589 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20061019T012201Z
DESCRIPTION:TICKET NUMBER: 589\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Thursday, October 19, 2006, 1:19 AM (0119)\nEND TIME: Thursday, October 19, 2006, 1:22 AM (0122)\nDESCRIPTION:  Peer APAN via JGN2 experienced a brief outage. APAN reports they had a problem with their TPR4 router. They have restarted the router and service has since be stable. Peer APAN is multi-homed.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=589&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20061025T202701Z
SUMMARY:  591 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20061025T232701Z
DESCRIPTION:TICKET NUMBER: 591\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2-Los Angeles OC-192 Circuit\n\nSTART TIME: Wednesday, October 25, 2006, 8:27 PM (2027)\nEND TIME: Wednesday, October 25, 2006, 11:27 PM (2327)\nDESCRIPTION:  Currently the TransPAC2-Los Angeles OC-192 Circuit is available.  APAN Technicians report the outage was caused by a fiber cut. The fiber cut has been repaired and service has since been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=591&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20061106T213201Z
SUMMARY:  599 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20061106T220901Z
DESCRIPTION:TICKET NUMBER: 599\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Monday, November 6, 2006, 9:32 PM (2132)\nEND TIME: Monday, November 6, 2006, 10:09 PM (2209)\nDESCRIPTION:  Peer APAN via JGN2 was unavailable to the TransPAC2 comunity. APAN engineers reported the outage was due to hardware issues.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=599&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20061109T111301Z
SUMMARY:  601 TransPAC2 Peer Abilene (LOSA) Outage Resolved
DTEND:20061109T111501Z
DESCRIPTION:TICKET NUMBER: 601\nOUTAGE TYPE: Software\nAFFECTED: Peer Abilene (LOSA)\n\nSTART TIME: Thursday, November 9, 2006, 11:13 AM (1113)\nEND TIME: Thursday, November 9, 2006, 11:15 AM (1115)\nDESCRIPTION:  TransPAC2 Peer Abilene (LOSA) experienced a brief outage. Abilene Engineers report the outage was caused by a software problem and are currently working with the vendor to resolve.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=601&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070322T045301Z
SUMMARY:  633 TransPAC2 Peer APAN Brief Outage Resolved
DTEND:20070322T050801Z
DESCRIPTION:TICKET NUMBER: 633\nOUTAGE TYPE: Hardware\nAFFECTED: Peer APAN\n\nSTART TIME: Thursday, March 22, 2007, 4:53 AM (0453)\nEND TIME: Thursday, March 22, 2007, 5:08 AM (0508)\nDESCRIPTION:  APAN was breifly unavailable to the TransPAC2 Community. APAN engineers report the outage was due to hardware problems. Service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=633&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070322T045301Z
SUMMARY:  634 TransPAC2 Peer APAN via JGN2 Outage
DTEND:20070322T050701Z
DESCRIPTION:TICKET NUMBER: 634\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Thursday, March 22, 2007, 4:53 AM (0453)\nEND TIME: Thursday, March 22, 2007, 5:07 AM (0507)\nDESCRIPTION:  APAN via JGN2 was unavailable to the TransPAC2 Community. APAN engineers have been contacted however, no cause for the outage has yet been provided.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=634&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070406T043701Z
SUMMARY:  639 TransPAC2 Peer Internet2 IP Network (LOSA) Available
DTEND:20070409T184801Z
DESCRIPTION:TICKET NUMBER: 639\nOUTAGE TYPE: Hardware\nAFFECTED: Peer Internet2 IP Network (LOSA)\n\nSTART TIME: Friday, April 6, 2007, 4:37 AM (0437)\nEND TIME: Monday, April 9, 2007, 6:48 PM (1848)\nDESCRIPTION:  Peer Internet2 IP Network (LOSA) is now available to the TransPAC2 community. Internet2 IP Network engineers restored the connection.  Internet2 IP Network is multihomed.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=639&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070503T150001Z
SUMMARY:  645 TransPAC2 NOC Email Account Outage Resolved
DTEND:20070503T191401Z
DESCRIPTION:TICKET NUMBER: 645\nOUTAGE TYPE: Undetermined\nAFFECTED: No Network Impact\n\nSTART TIME: Thursday, May 3, 2007, 3:00 PM (1500)\nEND TIME: Thursday, May 3, 2007, 7:14 PM (1914)\nDESCRIPTION:  The TransPAC2 NOC email account was unavailable. System administrators resolved the problem. Please resume contacting the TransPAC2 NOC via email or phone.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=645&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070519T181501Z
SUMMARY:  648 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20070520T084501Z
DESCRIPTION:TICKET NUMBER: 648\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: PEER:  APAN via JGN2\n\nSTART TIME: Saturday, May 19, 2007, 6:15 PM (1815)\nEND TIME: Sunday, May 20, 2007, 8:45 AM (0845)\nDESCRIPTION:  TransPAC2 peer APAN via JGN2  was unavailable to the community.  This was caused by a fiber cut in Salt Lake City.  The cable has been repaired and the service restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=648&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070521T161701Z
SUMMARY:  649 TransPAC2 Peers Internet2 (STTL), NLR, REANNZ, ESnet, and PNWGP Outage Resolved
DTEND:20070522T020301Z
DESCRIPTION:TICKET NUMBER: 649\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: Peers Internet2 (STTL), NLR, ESnet, REANNZ, and PNWGP\n\nSTART TIME: Monday, May 21, 2007, 4:17 PM (1617)\nEND TIME: Tuesday, May 22, 2007, 2:03 AM (0203)\nDESCRIPTION:  TransPAC2 peering with the listed peers was temporarily unavailable. TransPAC2 fiber provider, Level 3 communications, reports a fiber cut between Olympia, WA and Seattle was the cause. Splicing has been completed and service restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=649&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070622T051301Z
SUMMARY:  660 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20070622T051801Z
DESCRIPTION:TICKET NUMBER: 660\nOUTAGE TYPE: Software\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Friday, June 22, 2007, 5:13 AM (0513)\nEND TIME: Friday, June 22, 2007, 5:18 AM (0518)\nDESCRIPTION:  TransPAC2 peer APAN via JGN2 was unavailable to the community.  Outage was due to exceeding the maximum prefix-limit threshold.  The trouble was resolved by clearing BGP session.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=660&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070622T051301Z
SUMMARY:  661 TransPAC2 Peer ESnet Outage Resolved
DTEND:20070622T075301Z
DESCRIPTION:TICKET NUMBER: 661\nOUTAGE TYPE: Software\nAFFECTED: Peer ESnet\n\nSTART TIME: Friday, June 22, 2007, 5:13 AM (0513)\nEND TIME: Friday, June 22, 2007, 7:53 AM (0753)\nDESCRIPTION:  TransPAC2 peering with ESnet was unavailable to the community.  Outage was due to exceeding the maximum prefix-limit threshold. The trouble was resolved by clearing BGP session.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=661&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070705T231301Z
SUMMARY:  667 TransPAC2 IXP PacWave Available
DTEND:20070706T004101Z
DESCRIPTION:TICKET NUMBER: 667\nOUTAGE TYPE: Power\nAFFECTED: IXP Pacwave and its Peers\n\nSTART TIME: Thursday, July 5, 2007, 11:13 PM (2313)\nEND TIME: Friday, July 6, 2007, 12:41 AM (0041)\nDESCRIPTION:  IXP Pacwave and its peers were unavailable to the TransPAC2 community. DC power to collocation equipment in the Seattle PoP was lost. The DC battery system has been by-passed and power has been restored. Engineers are continuing to work on the problem to restore full stability to the system.  IXP is Multihomed.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=667&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070727T063001Z
SUMMARY:  675 TransPAC2 Peer APAN via JGN2 IPv6 Outage Available
DTEND:20070727T063501Z
DESCRIPTION:TICKET NUMBER: 675\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN via JGN2 IPv6\nTransPAC2-T320---LA;\nSTART TIME: Friday, July 27, 2007, 6:30 AM (0630)\nEND TIME: Friday, July 27, 2007, 6:35 AM (0635)\nDESCRIPTION:  Peer Peer APAN via JGN2 IPv6 was unavailable to the TransPAC2 Network community. Peer APAN via JGN2 IPv6 engineers have been contacted; however, the reason for the outage is still pending.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=675&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070731T091201Z
SUMMARY:  676 TransPAC2 Core Node Brief Outage Resolved
DTEND:20070731T091701Z
DESCRIPTION:TICKET NUMBER: 676\nOUTAGE TYPE: Hardware\nAFFECTED: All TransPAC2 connectivity\nTransPAC2-T320---LA;\nSTART TIME: Tuesday, July 31, 2007, 9:12 AM (0912)\nEND TIME: Tuesday, July 31, 2007, 9:17 AM (0917)\nDESCRIPTION:  TransPAC2 Core Node was briefly unavailable to the TransPAC2 community. TransPAC2 Engineers were notified and determined the cause to be hardware issues.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=676&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070717T185301Z
SUMMARY:  673 TransPAC2 Peer REANNZ IPv6 Available
DTEND:20070719T120201Z
DESCRIPTION:TICKET NUMBER: 673\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer REANNZ\n\nSTART TIME: Tuesday, July 17, 2007, 6:53 PM (1853)\nEND TIME: Thursday, July 19, 2007, 12:02 PM (1202)\nDESCRIPTION:  TransPAC2 Peer REANNZ IPv6 session is now available to the community. This may be related to maintenance completed and tracked in ticket 659:62.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=673&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070828T065801Z
SUMMARY:  687 TransPAC2 Peer APAN via JGN2 Available
DTEND:20070828T075901Z
DESCRIPTION:TICKET NUMBER: 687\nOUTAGE TYPE: Software\nAFFECTED: Peer APAN via JGN2*\n\nSTART TIME: Tuesday, August 28, 2007, 6:58 AM (0658)\nEND TIME: Tuesday, August 28, 2007, 7:59 AM (0759)\nDESCRIPTION:  TransPAC2 peer APAN via JGN2 is currently available to the community.APAN engineers rebooted their router, restoring service. *Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=687&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070828T173301Z
SUMMARY:  689 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20070829T045801Z
DESCRIPTION:TICKET NUMBER: 689\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2-Los Angeles OC-192 Circuit\n\nSTART TIME: Tuesday, August 28, 2007, 5:33 PM (1733)\nEND TIME: Wednesday, August 29, 2007, 4:58 AM (0458)\nDESCRIPTION:  TransPAC2-Los Angeles OC-192 Circuit was unavailable to the TransPAC2 Community. Circuit Provider, KDDI America LANOC investigated and determined this to be a fiber cut near Santa Clara, CA.  The carrier restored the fiber and the circuit.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=689&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070913T175401Z
SUMMARY:  694 TransPAC2 Peers Internet2 (STTL), NLR, and PNWG Brief Outage
DTEND:20070913T175601Z
DESCRIPTION:TICKET NUMBER: 694\nOUTAGE TYPE: Undetermined\nAFFECTED: Peers Internet2 (STTL), NLR, and PNWG\n\nSTART TIME: Thursday, September 13, 2007, 5:54 PM (1754)\nEND TIME: Thursday, September 13, 2007, 5:56 PM (1756)\nDESCRIPTION:  TransPAC2 Peers Internet2 (STTL), NLR, and PNWG were  briefly unavailable. Vendor Engineers are currently investigating but do not have a cause for the outage. Connectivity has been reestablished.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=694&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080517T135001Z
SUMMARY:  776 TransPAC2 Peer APAN via JGN2 Instability Resolved
DTEND:20080521T125501Z
DESCRIPTION:TICKET NUMBER: 776\nOUTAGE TYPE: Hardware\nAFFECTED: Peer APAN\n\nSTART TIME: Saturday, May 17, 2008, 1:50 PM (1350)\nEND TIME: Wednesday, May 21, 2008, 12:55 PM (1255)\nDESCRIPTION:  Peer APAN via JGN2 experienced instability to  the TransPAC2 community.  TransPAC2 Engineers,  with the assistance of an HP Technician, replaced a  defective optic module in the TransPAC2 6410 switch in  Los Angeles. The circuit was restored and has  remained stable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=776&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080221T012801Z
SUMMARY:  750 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20080221T012901Z
DESCRIPTION:TICKET NUMBER: 750\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Thursday, February 21, 2008, 1:28 AM (0128)\nEND TIME: Thursday, February 21, 2008, 1:29 AM (0129)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Circuit was briefly unavailable to the community.  KDDI America Engineers report their local carrier experienced a problem between Higashi-Shinagawa to Otemachi, but are unable to determine the exact cause of the outage.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=750&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080516T020901Z
SUMMARY:  774 TransPAC2 LOSA-Pacific Wave LOSA Circuit Outge Resolved
DTEND:20080517T133501Z
DESCRIPTION:TICKET NUMBER: 774\nOUTAGE TYPE: Hardware\nAFFECTED: Peers ESNET, Pacific Northwest Gigapop, Cenic, \nNREN\nTransPAC2 LOSA-JGN2 LOSA 10GigE\n\nSTART TIME: Friday, May 16, 2008, 2:09 AM (0209)\nEND TIME: Saturday, May 17, 2008, 1:35 PM (1335)\nDESCRIPTION:  Various Peers experienced instability to the  TransPAC2 community.  TransPAC2 Engineers, with the  assistance of an HP Technician, replaced a defective optic  module and the circuit was restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=774&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080327T233701Z
SUMMARY:  756 TransPAC2 IXP PacWave Brief Outage
DTEND:20080327T235701Z
DESCRIPTION:TICKET NUMBER: 756\nOUTAGE TYPE: Circuit---Other\nAFFECTED: IXP PacWave and its associated\nPeers\n\nSTART TIME: Thursday, March 27, 2008, 11:37 PM (2337)\nEND TIME: Thursday, March 27, 2008, 11:57 PM (2357)\nDESCRIPTION:  IXP PacWave and its associated peers were unavailable to the community.  PacWave Engineers were contacted and reported it was an inadvertent circuit outage due to other maintenance they were performing.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=756&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080303T052501Z
SUMMARY:  752 TransPAC2 Peer APAN JP Zebra Server Brief Outage Resolved
DTEND:20080303T054401Z
DESCRIPTION:TICKET NUMBER: 752\nOUTAGE TYPE: Power\nAFFECTED: Peer APAN JP Zebra Server\n\nSTART TIME: Monday, March 3, 2008, 5:25 AM (0525)\nEND TIME: Monday, March 3, 2008, 5:44 AM (0544)\nDESCRIPTION:  Transpac2 Peer APAN JP Zebra Server was briefly unavailable to the community. APAN engineers identified the issue to a maintenance they performed to replace a power supply on their equipment. Connectivity has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=752&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20080303T062001Z
SUMMARY:  752 TransPAC2 Peer APAN JP Zebra Server Brief Outage Resolved
DTEND:20080303T062101Z
DESCRIPTION:TICKET NUMBER: 752\nMAINTENANCE TYPE: \nAFFECTED: Peer APAN JP Zebra Server\n\nSTART TIME: Monday, March 3, 2008, 6:20 AM (0620)\nEND TIME: Monday, March 3, 2008, 6:21 AM (0621)\nDESCRIPTION:  Transpac2 Peer APAN JP Zebra Server was briefly unavailable to the community. APAN engineers identified the issue to a maintenance they performed to replace a power supply on their equipment. Connectivity has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=752&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20070925T104801Z
SUMMARY:  703 TransPAC2 Peer REANNZ IPv4 & IPv6 Available
DTEND:20070926T105701Z
DESCRIPTION:TICKET NUMBER: 703\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer REANNZ\n\nSTART TIME: Tuesday, September 25, 2007, 10:48 AM (1048)\nEND TIME: Wednesday, September 26, 2007, 10:57 AM (1057)\nDESCRIPTION:  TransPAC2 Peer REANNZ is currently available to the community. REANNZ engineers have been contacted; the reason for the outage was a path problem caused by their vendor.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=703&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20071106T120001Z
SUMMARY:  708 TransPAC2 Peers Internet2 (STTL), NLR, REANNZ, ESnet, NREN, & PNWGP Outage Resolved
DTEND:20071106T174201Z
DESCRIPTION:TICKET NUMBER: 708\nOUTAGE TYPE: Undetermined\nAFFECTED: Peers Internet2 (STTL)*, NLR, REANNZ, ESnet, NREN, & PNWGP\n\nSTART TIME: Tuesday, November 6, 2007, 12:00 PM (1200)\nEND TIME: Tuesday, November 6, 2007, 5:42 PM (1742)\nDESCRIPTION:  The above listed peers were unavailable. This was due to a failed maintenance to replace a card in Burney, CA. Engineers have restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=708&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20071119T021901Z
SUMMARY:  715 TransPAC2 Core Node T320 Outage Resolved
DTEND:20071119T032501Z
DESCRIPTION:TICKET NUMBER: 715\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node T320\nTransPAC2-T320---LA;\nSTART TIME: Monday, November 19, 2007, 2:19 AM (0219)\nEND TIME: Monday, November 19, 2007, 3:25 AM (0325)\nDESCRIPTION:  TransPAC2 Core Node T320 is now available. TransPAC2 engineers rebooted the router and restored connectivity. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=715&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20071203T124001Z
SUMMARY:  719 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20071206T023601Z
DESCRIPTION:TICKET NUMBER: 719\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Monday, December 3, 2007, 12:40 PM (1240)\nEND TIME: Thursday, December 6, 2007, 2:36 AM (0236)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA is now available to the community.  Repairs on teh GT-2 has been complete.  Connectivity has been restored. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=719&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20071205T031001Z
SUMMARY:  722 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20071205T061301Z
DESCRIPTION:TICKET NUMBER: 722\nOUTAGE TYPE: Power\nAFFECTED: Peer APAN via JGN2*\n\nSTART TIME: Wednesday, December 5, 2007, 3:10 AM (0310)\nEND TIME: Wednesday, December 5, 2007, 6:13 AM (0613)\nDESCRIPTION:  TransPAC2 Peer APAN via JGN2 was  unavailable to the community. The outage is due to an electrical power issue at Nedonna Beach CS. The carrier have restored the power.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=722&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080131T005501Z
SUMMARY:  737 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Resolved
DTEND:20080131T010501Z
DESCRIPTION:TICKET NUMBER: 737\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Thursday, January 31, 2008, 12:55 AM (0055)\nEND TIME: Thursday, January 31, 2008, 1:05 AM (0105)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Circuit was briefly un available. KDDI America Engineers report the problem was traced to an optical amplifier issue in Japan. Technicians have replaced the amplifier and the circuit remains stable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=737&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080430T232501Z
SUMMARY:  768 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outge Resolved
DTEND:20080501T004001Z
DESCRIPTION:TICKET NUMBER: 768\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Wednesday, April 30, 2008, 11:25 PM (2325)\nEND TIME: Thursday, May 1, 2008, 12:40 AM (0040)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Circuit was unavailable due to a faulty card in Emi, Japan. The card has been replaced and the circuit was  restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=768&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20080501T005601Z
SUMMARY:  768 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outge Resolved
DTEND:20080501T033201Z
DESCRIPTION:TICKET NUMBER: 768\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Thursday, May 1, 2008, 12:56 AM (0056)\nEND TIME: Thursday, May 1, 2008, 3:32 AM (0332)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Circuit was unavailable due to a faulty card in Emi, Japan. The card has been replaced and the circuit was  restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=768&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080507T051201Z
SUMMARY:  769 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20080507T053601Z
DESCRIPTION:TICKET NUMBER: 769\nOUTAGE TYPE: Software\nAFFECTED: Peer APAN\n\nSTART TIME: Wednesday, May 7, 2008, 5:12 AM (0512)\nEND TIME: Wednesday, May 7, 2008, 5:36 AM (0536)\nDESCRIPTION:  Peer APAN via JGN2 was unavailable to the TransPAC2 community. The outage was caused by the router that needed to be rebooted. The network is now restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=769&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080618T122001Z
SUMMARY:  793 TransPAC2 Various Peers Instability Resolved
DTEND:20080618T123001Z
DESCRIPTION:TICKET NUMBER: 793\nOUTAGE TYPE: Hardware\nAFFECTED: Peers I2 (STTL)\nNLR\nREANNZ\nESnet\nNREN\nPNWGP\n\nSTART TIME: Wednesday, June 18, 2008, 12:20 PM (1220)\nEND TIME: Wednesday, June 18, 2008, 12:30 PM (1230)\nDESCRIPTION:  Various peers are now stable to the TransPAC community.  TransPAC's carrier NLR had a  failing amp card between Soledad, CA and San Martin, CA  which caused this outage. Carrier NLR Engineering replaced the card and restore service. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=793&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20080618T135701Z
SUMMARY:  793 TransPAC2 Various Peers Instability Resolved
DTEND:20080618T140401Z
DESCRIPTION:TICKET NUMBER: 793\nMAINTENANCE TYPE: \nAFFECTED: Peers I2 (STTL)\nNLR\nREANNZ\nESnet\nNREN\nPNWGP\n\nSTART TIME: Wednesday, June 18, 2008, 1:57 PM (1357)\nEND TIME: Wednesday, June 18, 2008, 2:04 PM (1404)\nDESCRIPTION:  Various peers are now stable to the TransPAC community.  TransPAC's carrier NLR had a  failing amp card between Soledad, CA and San Martin, CA  which caused this outage. Carrier NLR Engineering replaced the card and restore service. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=793&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080702T225501Z
SUMMARY:  803 TransPAC2 IXP PacWave Outage Resolved
DTEND:20080702T232201Z
DESCRIPTION:TICKET NUMBER: 803\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peers Internet2 (SEAT), NLR, REANNZ, ESnet, NREN, and\nPNWGP\n\nSTART TIME: Wednesday, July 2, 2008, 10:55 PM (2255)\nEND TIME: Wednesday, July 2, 2008, 11:22 PM (2322)\nDESCRIPTION:  Transpac IXP PacWave was unavailable to the community. NLR Layer 1 NOC Engineering reports a vendor's field technician pulled the wrong fiber while conducting testing.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=803&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080712T090101Z
SUMMARY:  813 TransPAC2 Peer Internet2 IP Network Seattle Outage
DTEND:20080712T090601Z
DESCRIPTION:TICKET NUMBER: 813\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer Internet2 Seattle\n\nSTART TIME: Saturday, July 12, 2008, 9:01 AM (0901)\nEND TIME: Saturday, July 12, 2008, 9:06 AM (0906)\nDESCRIPTION:  Peer Internet2 Seattle was briefly unavailable to the community. Intenet2 Engineers have been contacted and are currently investigating; however, no reason for the outage has been determined.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=813&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080710T155801Z
SUMMARY:  810 TransPAC2 TOKY-TransPAC2 LOSA Circuit Outage Restored
DTEND:20080711T051801Z
DESCRIPTION:TICKET NUMBER: 810\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Thursday, July 10, 2008, 3:58 PM (1558)\nEND TIME: Friday, July 11, 2008, 5:18 AM (0518)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Circuit was unavailable to the community.  KDDI Engineers  have informed us that the outage was due to a  fiber cut in Los Angeles.  Repair work has been  completed and the circuit was restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=810&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080712T110201Z
SUMMARY:  814 TransPAC2 Various Peers Available
DTEND:20080714T193201Z
DESCRIPTION:TICKET NUMBER: 814\nOUTAGE TYPE: Hardware\nAFFECTED: Peers: Internet2 (STTL)\nNLR\nREANNZ\nESnet\nNREN\nPNWGP\n\nSTART TIME: Saturday, July 12, 2008, 11:02 AM (1102)\nEND TIME: Monday, July 14, 2008, 7:32 PM (1932)\nDESCRIPTION:  Various TransPAC2 Peers via PacWave are now available to the community. PacWave's carrier NLR replaced a failed card in Sunnyvale, CA resolving the issue. Services have returned.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=814&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080804T054501Z
SUMMARY:  833 TransPAC2 Peer REANNZ (STTL) Brief Outage
DTEND:20080804T055101Z
DESCRIPTION:TICKET NUMBER: 833\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer REANNZ\n\nSTART TIME: Monday, August 4, 2008, 5:45 AM (0545)\nEND TIME: Monday, August 4, 2008, 5:51 AM (0551)\nDESCRIPTION:  Peer REANNZ was briefly unavailable to the community. REANNZ engineers have been contacted; however, the reason for the outage is still pending.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=833&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080828T070001Z
SUMMARY:  843 TransPac2 Peer Internet2 Available
DTEND:20080828T171801Z
DESCRIPTION:TICKET NUMBER: 843\nOUTAGE TYPE: Hardware\nAFFECTED: Peer Internet2 *\n\nSTART TIME: Thursday, August 28, 2008, 7:00 AM (0700)\nEND TIME: Thursday, August 28, 2008, 5:18 PM (1718)\nDESCRIPTION:  Peer Internet2 is now stable to the community due to complications during their core node maintenance. Internet2 and PacWave engineers reported that cause of the outage was due to faulty hardware. *Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=843&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080909T040001Z
SUMMARY:  849 TransPAC2 Peer APAN via JGN2 Stable
DTEND:20080909T040201Z
DESCRIPTION:TICKET NUMBER: 849\nOUTAGE TYPE: Hardware\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Tuesday, September 9, 2008, 4:00 AM (0400)\nEND TIME: Tuesday, September 9, 2008, 4:02 AM (0402)\nDESCRIPTION:  Peer APAN via JGN2 is now stable to the community.  APAN Engineers reported the instability was due to hardware issues. Repairs have been made and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=849&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20080909T042201Z
SUMMARY:  849 TransPAC2 Peer APAN via JGN2 Stable
DTEND:20080909T042301Z
DESCRIPTION:TICKET NUMBER: 849\nMAINTENANCE TYPE: \nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Tuesday, September 9, 2008, 4:22 AM (0422)\nEND TIME: Tuesday, September 9, 2008, 4:23 AM (0423)\nDESCRIPTION:  Peer APAN via JGN2 is now stable to the community.  APAN Engineers reported the instability was due to hardware issues. Repairs have been made and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=849&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:3
DTSTART:20080909T044601Z
SUMMARY:  849 TransPAC2 Peer APAN via JGN2 Stable
DTEND:20080909T044701Z
DESCRIPTION:TICKET NUMBER: 849\nMAINTENANCE TYPE: \nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Tuesday, September 9, 2008, 4:46 AM (0446)\nEND TIME: Tuesday, September 9, 2008, 4:47 AM (0447)\nDESCRIPTION:  Peer APAN via JGN2 is now stable to the community.  APAN Engineers reported the instability was due to hardware issues. Repairs have been made and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=849&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20080928T095101Z
SUMMARY:  857 TransPAC2 Peer REANNZ Brief Outage
DTEND:20080928T095801Z
DESCRIPTION:TICKET NUMBER: 857\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer REANNZ\n\nSTART TIME: Sunday, September 28, 2008, 9:51 AM (0951)\nEND TIME: Sunday, September 28, 2008, 9:58 AM (0958)\nDESCRIPTION:  Peer REANNZ was unavailable to the community. The REANNZ engineers have been contacted, however, the reason for the outage is not known as yet.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=857&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081012T050201Z
SUMMARY:  863 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20081012T052001Z
DESCRIPTION:TICKET NUMBER: 863\nOUTAGE TYPE: Software\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Sunday, October 12, 2008, 5:02 AM (0502)\nEND TIME: Sunday, October 12, 2008, 5:20 AM (0520)\nDESCRIPTION:  Peer APAN was unavailable to the community. The outage was due to the rebooting of Jm-e600 router. The service is not restored. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=863&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081017T151201Z
SUMMARY:  864 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081018T040201Z
DESCRIPTION:TICKET NUMBER: 864\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\nPeer APAN\n\nSTART TIME: Friday, October 17, 2008, 3:12 PM (1512)\nEND TIME: Saturday, October 18, 2008, 4:02 AM (0402)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unavailable.  KDDI Engineers reported that this outage was caused by a fiber cut between Los Angeles, CA and  Hillsboro, Oregon.  The fiber has been repaired and the service restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=864&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081023T181901Z
SUMMARY:  868 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081023T182101Z
DESCRIPTION:TICKET NUMBER: 868\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\n\nSTART TIME: Thursday, October 23, 2008, 6:19 PM (1819)\nEND TIME: Thursday, October 23, 2008, 6:21 PM (1821)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unavailable to the TransPAC2 Community.  KDDI Engineers reported there was a fiber outage between San Francisco, CA and Oakland, CA.  Service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=868&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081025T024201Z
SUMMARY:  871 TransPAC2 Various Peers via PacWave Available
DTEND:20081025T033101Z
DESCRIPTION:TICKET NUMBER: 871\nOUTAGE TYPE: Undetermined\nAFFECTED: ESnet, REAANZ, NREN, PNWGP, AARnet\n\nSTART TIME: Saturday, October 25, 2008, 2:42 AM (0242)\nEND TIME: Saturday, October 25, 2008, 3:31 AM (0331)\nDESCRIPTION:  Various Peers via PacWave was unavailable to the community. PacWave engineers are currently investigating a high CPU utilization on the Los Angeles PWAVE switch.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=871&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081027T153701Z
SUMMARY:  873 TransPAC2 Various Peers via PacWave Brief Outage
DTEND:20081027T153901Z
DESCRIPTION:TICKET NUMBER: 873\nOUTAGE TYPE: Undetermined\nAFFECTED: Peers I2 (STTL)*, NLR, REANNZ, ESnet, NREN, and PNWGP\n\n\nSTART TIME: Monday, October 27, 2008, 3:37 PM (1537)\nEND TIME: Monday, October 27, 2008, 3:39 PM (1539)\nDESCRIPTION:  Various Peers via PacWave was briefly unavailable to the community. PacWave engineers have been contacted, however, the reason for the outage has not been provided.  *Denotes multihomed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=873&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081103T165101Z
SUMMARY:  875 TransPAC2 Peer UltraLight Outage Resolved
DTEND:20081103T180801Z
DESCRIPTION:TICKET NUMBER: 875\nOUTAGE TYPE: Software\nAFFECTED: Peer Ultralight\n\nSTART TIME: Monday, November 3, 2008, 4:51 PM (1651)\nEND TIME: Monday, November 3, 2008, 6:08 PM (1808)\nDESCRIPTION:  Peer Ultralight is now available to the community. Ultralight engineers have Ultralight engineers have have corrected, some software issues, thereby restoring connectivity. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=875&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081110T013701Z
SUMMARY:  877 TransPAC2 Peer APAN via TransPAC2 Outage Resolved
DTEND:20081110T071301Z
DESCRIPTION:TICKET NUMBER: 877\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peer APAN via TransPAC2*\n\nSTART TIME: Monday, November 10, 2008, 1:37 AM (0137)\nEND TIME: Monday, November 10, 2008, 7:13 AM (0713)\nDESCRIPTION:  Peer APAN via TransPAC2 is now stable. APAN engineers have stated that the connection is available and the outage was the result of errors received by a local provider's equipment. An adjustment was made to correct the equipment and the errors have stopped.  *denoted multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=877&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081111T014401Z
SUMMARY:  878 TransPAC2 Various Peers via PacWave Outage Resolved
DTEND:20081111T040201Z
DESCRIPTION:TICKET NUMBER: 878\nOUTAGE TYPE: Software\nAFFECTED: Peers Internet2 & ESnet\n\nSTART TIME: Tuesday, November 11, 2008, 1:44 AM (0144)\nEND TIME: Tuesday, November 11, 2008, 4:02 AM (0402)\nDESCRIPTION:  The above listed peers are now available to the community. Respective PacWave and CENIC engineers have been contacted and it is believed that the outage stemmed from high utilization on a CENIC Sunnyvale router.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=878&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081118T103801Z
SUMMARY:  880 TransPAC2 Peer REANNZ Brief Outage Resolved
DTEND:20081118T104501Z
DESCRIPTION:TICKET NUMBER: 880\nOUTAGE TYPE: Hardware\nAFFECTED: Peer REANNZ\n\nSTART TIME: Tuesday, November 18, 2008, 10:38 AM (1038)\nEND TIME: Tuesday, November 18, 2008, 10:45 AM (1045)\nDESCRIPTION:  Peer REANNZ was briefly unavailable.  REANNZ Engineers have been contacted and report the outage was due to memory issues on their router. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=880&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081118T230201Z
SUMMARY:  881 TransPAC2 Various Peers via Pacwave Brief Outage Update
DTEND:20081118T230301Z
DESCRIPTION:TICKET NUMBER: 881\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peers I2 (SEAT), NLR, REANNZ, ESnet, NREN, and PNWGP\n\nSTART TIME: Tuesday, November 18, 2008, 11:02 PM (2302)\nEND TIME: Tuesday, November 18, 2008, 11:03 PM (2303)\nDESCRIPTION:  Pacwave was briefly unavailable to the TransPAC2 community. The customer's service provider have determined that the Dugene, OR site was the source of the problem; however, no reason for the outage has been given.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=881&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081125T011001Z
SUMMARY:  886 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Brief Outage
DTEND:20081125T011101Z
DESCRIPTION:TICKET NUMBER: 886\nOUTAGE TYPE: Undetermined\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Tuesday, November 25, 2008, 1:10 AM (0110)\nEND TIME: Tuesday, November 25, 2008, 1:11 AM (0111)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was briefly unavailable to the community. Circuit provider KDDI America investigated, but was unable to determine the cause of the outage.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=886&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081119T212501Z
SUMMARY:  882 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20081120T021001Z
DESCRIPTION:TICKET NUMBER: 882\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Wednesday, November 19, 2008, 9:25 PM (2125)\nEND TIME: Thursday, November 20, 2008, 2:10 AM (0210)\nDESCRIPTION:  Peer APAN via JGN2 was unavailable to the community. APAN Engineers reported that the issue was caused by a fiber cut between Sunnyvale, CA and Houston, TX. APAN's fiber provider has temporarily moved them to new fiber while they repair the cut.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=882&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081121T060301Z
SUMMARY:  884 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081121T060401Z
DESCRIPTION:TICKET NUMBER: 884\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone\nCircuit\nPeer APAN\n\nSTART TIME: Friday, November 21, 2008, 6:03 AM (0603)\nEND TIME: Friday, November 21, 2008, 6:04 AM (0604)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unstable to the community.  KDDI Engineers replaced transmission equipment on an underwater portion of the circuit. This was successful and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=884&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20081121T062601Z
SUMMARY:  884 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081121T062701Z
DESCRIPTION:TICKET NUMBER: 884\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone\nCircuit\nPeer APAN\n\nSTART TIME: Friday, November 21, 2008, 6:26 AM (0626)\nEND TIME: Friday, November 21, 2008, 6:27 AM (0627)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unstable to the community.  KDDI Engineers replaced transmission equipment on an underwater portion of the circuit. This was successful and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=884&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:3
DTSTART:20081121T102701Z
SUMMARY:  884 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081121T102801Z
DESCRIPTION:TICKET NUMBER: 884\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone\nCircuit\nPeer APAN\n\nSTART TIME: Friday, November 21, 2008, 10:27 AM (1027)\nEND TIME: Friday, November 21, 2008, 10:28 AM (1028)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unstable to the community.  KDDI Engineers replaced transmission equipment on an underwater portion of the circuit. This was successful and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=884&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:4
DTSTART:20081121T190101Z
SUMMARY:  884 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081122T052801Z
DESCRIPTION:TICKET NUMBER: 884\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone\nCircuit\nPeer APAN\n\nSTART TIME: Friday, November 21, 2008, 7:01 PM (1901)\nEND TIME: Saturday, November 22, 2008, 5:28 AM (0528)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unstable to the community.  KDDI Engineers replaced transmission equipment on an underwater portion of the circuit. This was successful and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=884&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081122T231901Z
SUMMARY:  885 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081122T232001Z
DESCRIPTION:TICKET NUMBER: 885\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Saturday, November 22, 2008, 11:19 PM (2319)\nEND TIME: Saturday, November 22, 2008, 11:20 PM (2320)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. KDDI Engineers reported that a failing card in Hillsboro, OR was responsible for the instability. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=885&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20081122T232201Z
SUMMARY:  885 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081122T232301Z
DESCRIPTION:TICKET NUMBER: 885\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Saturday, November 22, 2008, 11:22 PM (2322)\nEND TIME: Saturday, November 22, 2008, 11:23 PM (2323)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. KDDI Engineers reported that a failing card in Hillsboro, OR was responsible for the instability. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=885&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:3
DTSTART:20081122T234301Z
SUMMARY:  885 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081122T234401Z
DESCRIPTION:TICKET NUMBER: 885\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Saturday, November 22, 2008, 11:43 PM (2343)\nEND TIME: Saturday, November 22, 2008, 11:44 PM (2344)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. KDDI Engineers reported that a failing card in Hillsboro, OR was responsible for the instability. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=885&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:4
DTSTART:20081123T014801Z
SUMMARY:  885 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081123T035501Z
DESCRIPTION:TICKET NUMBER: 885\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Circuit\n\nSTART TIME: Sunday, November 23, 2008, 1:48 AM (0148)\nEND TIME: Sunday, November 23, 2008, 3:55 AM (0355)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. KDDI Engineers reported that a failing card in Hillsboro, OR was responsible for the instability. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=885&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081129T182201Z
SUMMARY:  887 TransPAC2 Peer Internet2 (LOSA) Available
DTEND:20081129T182901Z
DESCRIPTION:TICKET NUMBER: 887\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer Internet2 IP Network (LOSA)\n\nSTART TIME: Saturday, November 29, 2008, 6:22 PM (1822)\nEND TIME: Saturday, November 29, 2008, 6:29 PM (1829)\nDESCRIPTION:  TransPAC2 Peer Internet2 IP Network (LOSA) was briefly unavailable to the community. Internet2 Engineers are currently investigating software issues with the vendor that might have contributed to this event.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=887&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081206T221101Z
SUMMARY:  890 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081206T221201Z
DESCRIPTION:TICKET NUMBER: 890\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Saturday, December 6, 2008, 10:11 PM (2211)\nEND TIME: Saturday, December 6, 2008, 10:12 PM (2212)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community.  KDDI America reported that the outage was due to a failed card in Japan. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=890&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20081207T195301Z
SUMMARY:  890 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081207T210201Z
DESCRIPTION:TICKET NUMBER: 890\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Sunday, December 7, 2008, 7:53 PM (1953)\nEND TIME: Sunday, December 7, 2008, 9:02 PM (2102)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community.  KDDI America reported that the outage was due to a failed card in Japan. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=890&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:3
DTSTART:20081207T222201Z
SUMMARY:  890 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081207T223301Z
DESCRIPTION:TICKET NUMBER: 890\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Sunday, December 7, 2008, 10:22 PM (2222)\nEND TIME: Sunday, December 7, 2008, 10:33 PM (2233)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community.  KDDI America reported that the outage was due to a failed card in Japan. The card has been replaced and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=890&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081208T010701Z
SUMMARY:  891 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081208T011101Z
DESCRIPTION:TICKET NUMBER: 891\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Monday, December 8, 2008, 1:07 AM (0107)\nEND TIME: Monday, December 8, 2008, 1:11 AM (0111)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. Fiber provider KDDI America determined a failing card in Hillsboro, OR caused the instability. The carrier has moved the circuit to a spare frequency and restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=891&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20081208T043901Z
SUMMARY:  891 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081208T044001Z
DESCRIPTION:TICKET NUMBER: 891\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Monday, December 8, 2008, 4:39 AM (0439)\nEND TIME: Monday, December 8, 2008, 4:40 AM (0440)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. Fiber provider KDDI America determined a failing card in Hillsboro, OR caused the instability. The carrier has moved the circuit to a spare frequency and restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=891&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:3
DTSTART:20081208T073401Z
SUMMARY:  891 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081208T073801Z
DESCRIPTION:TICKET NUMBER: 891\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Monday, December 8, 2008, 7:34 AM (0734)\nEND TIME: Monday, December 8, 2008, 7:38 AM (0738)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. Fiber provider KDDI America determined a failing card in Hillsboro, OR caused the instability. The carrier has moved the circuit to a spare frequency and restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=891&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:4
DTSTART:20081208T074101Z
SUMMARY:  891 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081208T074201Z
DESCRIPTION:TICKET NUMBER: 891\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Monday, December 8, 2008, 7:41 AM (0741)\nEND TIME: Monday, December 8, 2008, 7:42 AM (0742)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now stable to the community. Fiber provider KDDI America determined a failing card in Hillsboro, OR caused the instability. The carrier has moved the circuit to a spare frequency and restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=891&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081209T041601Z
SUMMARY:  892 TransPAC2 IXP PacWave Brief Outage
DTEND:20081209T041801Z
DESCRIPTION:TICKET NUMBER: 892\nOUTAGE TYPE: Circuit---Other\nAFFECTED: IXP PacWave\n\nSTART TIME: Tuesday, December 9, 2008, 4:16 AM (0416)\nEND TIME: Tuesday, December 9, 2008, 4:18 AM (0418)\nDESCRIPTION:  IXP PacWave was briefly unavailable to the community.  PacWave's fiber provider has determined the outage was caused by a probable fiber bump.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=892&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081209T042001Z
SUMMARY:  893 TransPAC2 Peer Pacific Northwest GigaPoP Available
DTEND:20081209T073201Z
DESCRIPTION:TICKET NUMBER: 893\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer Pacific Northwest GigaPoP\n\nSTART TIME: Tuesday, December 9, 2008, 4:20 AM (0420)\nEND TIME: Tuesday, December 9, 2008, 7:32 AM (0732)\nDESCRIPTION:  Pacific Northwest GigaPoP is now available. PNWGP Engineers have been contacted and are currently investigating; however, no reason for the outage has been provided.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=893&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081210T093801Z
SUMMARY:  896 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081210T125101Z
DESCRIPTION:TICKET NUMBER: 896\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA\n\nSTART TIME: Wednesday, December 10, 2008, 9:38 AM (0938)\nEND TIME: Wednesday, December 10, 2008, 12:51 PM (1251)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. Circuit provider KDDI America reported that that the outage was due to a bad card that the LEC (Local Exchange Carrier). The card has been replaced and connectivity has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=896&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20081218T170201Z
SUMMARY:  897 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20081218T175501Z
DESCRIPTION:TICKET NUMBER: 897\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Thursday, December 18, 2008, 5:02 PM (1702)\nEND TIME: Thursday, December 18, 2008, 5:55 PM (1755)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was briefly unavailable to the community.  KDDI engineers detected alarms on the southern submarine route between Tokyo and Los Angeles. The outage was determined to be carrier maintenance. 
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=897&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090104T004601Z
SUMMARY:  903 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090104T013901Z
DESCRIPTION:TICKET NUMBER: 903\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA*\n\nSTART TIME: Sunday, January 4, 2009, 12:46 AM (0046)\nEND TIME: Sunday, January 4, 2009, 1:39 AM (0139)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community.  According to KDDI America, the outage was due to a faulty DWDM optical amplifier in Hamamatsu, Japan. The amplifier has been replaced and service has been restored. *Traffic rerouted during this outage.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=903&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20090104T050801Z
SUMMARY:  903 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090104T053001Z
DESCRIPTION:TICKET NUMBER: 903\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA*\n\nSTART TIME: Sunday, January 4, 2009, 5:08 AM (0508)\nEND TIME: Sunday, January 4, 2009, 5:30 AM (0530)\nDESCRIPTION:  TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community.  According to KDDI America, the outage was due to a faulty DWDM optical amplifier in Hamamatsu, Japan. The amplifier has been replaced and service has been restored. *Traffic rerouted during this outage.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=903&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090111T041201Z
SUMMARY:  905 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20090113T083501Z
DESCRIPTION:TICKET NUMBER: 905\nOUTAGE TYPE: Hardware\nAFFECTED: Peer APAN via JGN2\n\nSTART TIME: Sunday, January 11, 2009, 4:12 AM (0412)\nEND TIME: Tuesday, January 13, 2009, 8:35 AM (0835)\nDESCRIPTION:  Peer APAN via JGN2 is now available. APAN Engineers report a failing power unit has been replaced.  All service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=905&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090123T160201Z
SUMMARY:  910 TransPAC2 Peer APAN via JGN2 Outage Resolved
DTEND:20090123T162001Z
DESCRIPTION:TICKET NUMBER: 910\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer APAN* via JGN2\n\nSTART TIME: Friday, January 23, 2009, 4:02 PM (1602)\nEND TIME: Friday, January 23, 2009, 4:20 PM (1620)\nDESCRIPTION:  Peer APAN is now available to the community. APAN engineers reported that the outage was due to a router reboot  *Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=910&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090130T202801Z
SUMMARY:  914 TransPAC2 Peers Internet2 (SEAT), NLR, REANNZ, ESnet, NREN, and PNWGP Brief Outage Resolved
DTEND:20090130T203201Z
DESCRIPTION:TICKET NUMBER: 914\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peers I2 (STTL)*, NLR, REANNZ, ESnet, NREN, and PNWGP\n\nSTART TIME: Friday, January 30, 2009, 8:28 PM (2028)\nEND TIME: Friday, January 30, 2009, 8:32 PM (2032)\nDESCRIPTION:  The above listed peers were briefly unavailable to the community. Customers fiber provider reports the outage was due to a fiber bump.  *Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=914&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090213T074001Z
SUMMARY:  921 TransPAC2 Peers Internet2 (STTL), NLR, ESnet, and Pacific Northwest GigaPoP Emergency Maintenance Completed
DTEND:20090213T100001Z
DESCRIPTION:TICKET NUMBER: 921\nOUTAGE TYPE: Hardware\nAFFECTED: Peers Internet2* (STTL), NLR, ESnet, and Pacific\nNorthwest GigaPoP\n\nSTART TIME: Friday, February 13, 2009, 7:40 AM (0740)\nEND TIME: Friday, February 13, 2009, 10:00 AM (1000)\nDESCRIPTION:  Peers Internet2 (STTL), NLR, ESnet, and Pacific Northwest GigaPoP continue to be unavailable to the community following this maintenance.  Subsequent outages will be tracked in 922:62. *Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=921&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090213T100001Z
SUMMARY:  922 TransPAC2 Peers Internet2 (STTL), NLR, ESnet, and Pacific Northwest GigaPoP Outage Resolved
DTEND:20090213T124001Z
DESCRIPTION:TICKET NUMBER: 922\nOUTAGE TYPE: Hardware\nAFFECTED: Peers Internet2* (STTL), NLR, ESnet, and Pacific\nNorthwest GigaPoP\n\nSTART TIME: Friday, February 13, 2009, 10:00 AM (1000)\nEND TIME: Friday, February 13, 2009, 12:40 PM (1240)\nDESCRIPTION:  Peers Internet2 (STTL), NLR, ESnet, and Pacific Northwest GigaPoP are now available to the community. The outage was due to issues on the customer's carrier following emergency maintenance.  The carrier reports this issue is resolved. * Denotes multi-homed status
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=922&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090301T024601Z
SUMMARY:  929 TransPAC2 Peer ESnet (LOSA) Outage Resolved
DTEND:20090301T043001Z
DESCRIPTION:TICKET NUMBER: 929\nOUTAGE TYPE: Circuit---Other\nAFFECTED: ESnet (LOSA)\n\nSTART TIME: Sunday, March 1, 2009, 2:46 AM (0246)\nEND TIME: Sunday, March 1, 2009, 4:30 AM (0430)\nDESCRIPTION:  Peer ESnet is unavailable to the TransPAC2 community. Level(3) Communications was contacted to restore a faulty cross-connect in Sunnyvale, CA.  Service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=929&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090318T102901Z
SUMMARY:  931 TransPAC2 Various Peers via PacWave Outage Resolved
DTEND:20090318T105001Z
DESCRIPTION:TICKET NUMBER: 931\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Peers I2 (STTL)*, NLR (SEAT)*, REANNZ, ESnet, NREN, and\nPNWGP\n\nSTART TIME: Wednesday, March 18, 2009, 10:29 AM (1029)\nEND TIME: Wednesday, March 18, 2009, 10:50 AM (1050)\nDESCRIPTION:  The above listed peers were unavailable while PacWave's fiber provider performed maintenance in Freemont, CA. This maintenance has been completed. *Denotes the peer is multihomed and remains reachable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=931&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090420T221401Z
SUMMARY:  939 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090421T013101Z
DESCRIPTION:TICKET NUMBER: 939\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Monday, April 20, 2009, 10:14 PM (2214)\nEND TIME: Tuesday, April 21, 2009, 1:31 AM (0131)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available. KDDI America reports the outage was caused by a failing card in Santa Clara, CA. Their back haul circuit provider has replaced the card and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=939&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090421T181001Z
SUMMARY:  940 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090421T195001Z
DESCRIPTION:TICKET NUMBER: 940\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Tuesday, April 21, 2009, 6:10 PM (1810)\nEND TIME: Tuesday, April 21, 2009, 7:50 PM (1950)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI America reports that their back haul circuit provider had fiber issues between Portland, OR and Santa Clara, CA.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=940&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090422T194801Z
SUMMARY:  941 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090422T232301Z
DESCRIPTION:TICKET NUMBER: 941\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Wednesday, April 22, 2009, 7:48 PM (1948)\nEND TIME: Wednesday, April 22, 2009, 11:23 PM (2323)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit was unavailable to the community. Transpac2 engineers report the outage was due to a Optical amplifier failure. The fiber provider replaced the failed amplifier and restored service.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=941&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090424T142301Z
SUMMARY:  945 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090425T010101Z
DESCRIPTION:TICKET NUMBER: 945\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Friday, April 24, 2009, 2:23 PM (1423)\nEND TIME: Saturday, April 25, 2009, 1:01 AM (0101)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI Engineers identified a fiber cut between Tokyo and Toyohashi, JP. The damaged fiber has been repaired and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=945&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090430T041901Z
SUMMARY:  948 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Available
DTEND:20090430T044201Z
DESCRIPTION:TICKET NUMBER: 948\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Thursday, April 30, 2009, 4:19 AM (0419)\nEND TIME: Thursday, April 30, 2009, 4:42 AM (0442)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI Engineers investigated but were unable to determine a cause of the outage.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=948&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090512T043501Z
SUMMARY:  952 TransPAC2 Peer CENIC (LOSA) Instability Resolved
DTEND:20090514T202301Z
DESCRIPTION:TICKET NUMBER: 952\nOUTAGE TYPE: Undetermined\nAFFECTED: Peer CENIC (LOSA)\n\nSTART TIME: Tuesday, May 12, 2009, 4:35 AM (0435)\nEND TIME: Thursday, May 14, 2009, 8:23 PM (2023)\nDESCRIPTION:  Peer CENIC is now available to the community.  Internet2 engineers worked with CENIC  engineers to restore stability. All work has been  completed.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=952&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090522T125901Z
SUMMARY:  954 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090522T132201Z
DESCRIPTION:TICKET NUMBER: 954\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Friday, May 22, 2009, 12:59 PM (1259)\nEND TIME: Friday, May 22, 2009, 1:22 PM (1322)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI America reports the outage was caused when the JGN2 circuit went down and traffic was temporarily transitioned to it.  No further outages are expected.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=954&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090528T211601Z
SUMMARY:  956 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090529T002701Z
DESCRIPTION:TICKET NUMBER: 956\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Backbone Circuit TOKY-TransPAC2 LOSA\n\nSTART TIME: Thursday, May 28, 2009, 9:16 PM (2116)\nEND TIME: Friday, May 29, 2009, 12:27 AM (0027)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI-America reported a problem with hardware in Hillsboro, OR. The outage has been resolved and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=956&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090605T005001Z
SUMMARY:  958 TransPAC2 Peer APAN JP Zebra Server Available
DTEND:20090605T015901Z
DESCRIPTION:TICKET NUMBER: 958\nOUTAGE TYPE: Software\nAFFECTED: rtr.losa.transpac2.net\n\nSTART TIME: Friday, June 5, 2009, 12:50 AM (0050)\nEND TIME: Friday, June 5, 2009, 1:59 AM (0159)\nDESCRIPTION:  BGP to APAN Zebra Server is up.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=958&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090609T053001Z
SUMMARY:  959 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090609T060201Z
DESCRIPTION:TICKET NUMBER: 959\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit\n\nSTART TIME: Tuesday, June 9, 2009, 5:30 AM (0530)\nEND TIME: Tuesday, June 9, 2009, 6:02 AM (0602)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit is now available to the community. KDDI America reports the outage was caused by brief power supply issues in Japan.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=959&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090611T221501Z
SUMMARY:  960 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090611T232801Z
DESCRIPTION:TICKET NUMBER: 960\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone \nCircuit\n\nSTART TIME: Thursday, June 11, 2009, 10:15 PM (2215)\nEND TIME: Thursday, June 11, 2009, 11:28 PM (2328)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA  Backbone Circuit is now available to the community. KDDI America  reports their subsea cable carrier determined a failed  DCD Distribution Module caused the outages.  Maintenance to perform permanent repairs may need to be  scheduled at a later date; however, the circuit is currently up  and stable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=960&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:2
DTSTART:20090612T005701Z
SUMMARY:  960 TransPAC2 TOKY-TransPAC2 LOSA Backbone Circuit Outage Resolved
DTEND:20090612T011501Z
DESCRIPTION:TICKET NUMBER: 960\nMAINTENANCE TYPE: \nAFFECTED: TransPAC2 TOKY-TransPAC2 LOSA Backbone \nCircuit\n\nSTART TIME: Friday, June 12, 2009, 12:57 AM (0057)\nEND TIME: Friday, June 12, 2009, 1:15 AM (0115)\nDESCRIPTION:  The TransPAC2 TOKY-TransPAC2 LOSA  Backbone Circuit is now available to the community. KDDI America  reports their subsea cable carrier determined a failed  DCD Distribution Module caused the outages.  Maintenance to perform permanent repairs may need to be  scheduled at a later date; however, the circuit is currently up  and stable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=960&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090701T092801Z
SUMMARY:  963 TransPAC2 Various Peers via IXP PacWave Available
DTEND:20090701T113201Z
DESCRIPTION:TICKET NUMBER: 963\nOUTAGE TYPE: Undetermined\nAFFECTED: Peers I2 (SEAT)*, NLR (SEAT)*, REANNZ, ESnet, \nNREN, and\nPNWGP\n\nSTART TIME: Wednesday, July 1, 2009, 9:28 AM (0928)\nEND TIME: Wednesday, July 1, 2009, 11:32 AM (1132)\nDESCRIPTION:  The above listed peers via PacWave is currently available to the community. PacWave's service provider states that a vendor fiber cut was the cause for the outage.  *Denoted Peers are multihomed and therefore remain reachable.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=963&proj=62
END:VEVENT
BEGIN:VEVENT
SEQUENCE:1
DTSTART:20090701T215901Z
SUMMARY:  964 TransPAC2 Various Peers via IXP PacWave Available
DTEND:20090701T224801Z
DESCRIPTION:TICKET NUMBER: 964\nOUTAGE TYPE: Circuit---Other\nAFFECTED: TransPAC2 Various Peers via IXP PacWave\n\nSTART TIME: Wednesday, July 1, 2009, 9:59 PM (2159)\nEND TIME: Wednesday, July 1, 2009, 10:48 PM (2248)\nDESCRIPTION:  TransPAC2 Various Peers via IXP were unavailable. This was due to a Level(3) Communications technician performing a change request in Kelso, WA. The change was not intended to be service impacting. No further outages are expected. The outage has been resolved and service has been restored.
URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/view.cgi?tick=964&proj=62
END:VEVENT
END:VCALENDAR