Penn State shield
Skip to content Skip to search

Headlines

ITS Alert - Resolved: Internet2 connectivity

/alerts

ITS Alerts by Date


ITS Alerts by Service

ITS Alerts by Location

  • red boxCurrent Alert
  • green boxResolved Alert
  • orange boxFuture Alert

Resolved: Internet2 connectivity

Last updated on April 26, 2013 at 12:28PM

Update on April 26, 2013 at 12:28PM

Issue has been resolved.

\"\"Internet2 sent confirmation that Level3 completed fiber splicing work last
night, 25-Apr-13, at ~9:30pmET. No further outages are expected.

Update on April 25, 2013 at 10:14PM

ISP update:

\"Services that use Internet2 became available at ~9pmET, 25-Apr-13.
However, repair of the fiber cut in the McLean, VA, area is ongoing and
may result in additional outages/instability until Level3 has completed
their work.\"

We are continuing to monitor, and can confirm speed degradation problems at this point have been resolved and I2 connectivity has been restored. We will update when work has been completed.

Update on April 25, 2013 at 6:44PM

We have confirmed with the ISP that this outage is causing some degraded speed issues to internet sites. We will continue to monitor these issues and update as more information is available.

Original Alert

We received notice from our I2 ISP:

"Because of a suspected fiber cut in McLean, Virginia, services that use Internet2 are currently down. These include the Internet2 IP network, TR-CPS and Google peering. R&E traffic will failover to NLR if possible. Google and TR-CPS traffic will take the commodity Internet.

There is as yet no time estimate from Internet2 for restoration of services."

Due to this outage some site connectivity may be degraded or unavailable.

We will update as more information becomes available.

For more information, please contact Network Operations Center (814-865-4662).


Back to ITS Alerts

Impact Information

  • Incident Type:
    Unexpected Outage
  • Services affected:
    Network
  • Locations affected:
    All locations
  • Began on:
    April 25, 2013 at 4:59PM
  • Issue Resolved:
    April 26, 2013 at 12:27PM