Updates on open issues.

Network Status

Current Network Issues

All monitored networks are currently operating normally.

If you’re experiencing an issue on our network,
please call 410.637.3707 or 850.622.0622 to report a problem,
or click here to start a support case.

Recent Updates

March 1, 4:38PM – All connections routed through our mid-Baltimore distribution center have been restored.

March 1, 3:34PM – Most connections routed through our mid-Baltimore distribution center have been restored. We are continuing to work on an issue affection the Cecil, Winthrop, and University One properties.

March 1, 2:54PM – We are currently experiencing a problem at our mid-Baltimore distribution center. We have dispatched a technician and are awaiting further details from the site.

February 7, 3:42PM – Our primary authentication system had to be rebooted this afternoon, and some routers have not re-authenticated. If you are unable to connect to the Internet, please power-cycle your router (remove the power cord, then put it back in), wait 3-5 minutes, and your router should re-authenticate. If that doesn’t work, please call us at 410.637.3707.

January 30, 10:42AM – Most customers affected by this morning’s core routing issue have had service restored, and we are working with individual customers to reach complete resolution. If you are experiencing any issue and have not heard from someone at Port Networks, please call 410.637.3707.

January 30, 9:42AM – Our apologies, the issue affecting central and eastern Baltimore locations has proven more complex than we originally expected. We have technicians replacing a core routing engine to restore service. New estimated time of resolution is 1030EST.

January 30, 4:07AM – An unexpected power cut at one of our core locations is impacting service for customers in central Baltimore. Technicians are working on the issue. Estimated time of resolution is 0800EST.

January 7, 7:35PM – Service has been restored for the segment of our network in northern Baltimore that was experiencing an issue.

January 7, 7:05PM – We are currently investigating a problem affecting a segment of our network in northern Baltimore. More details will be posted as soon as available.

November 15, 8:20PM – Repairs to the cut fiber are complete, and data is now following normal routes between Baltimore and the Internet exchange points in Northern Virginia.

November 15, 8:00PM – Repair crews at the site of the fiber cut report that replacement fiber has been pulled through new duct, both ends of the damaged cable have been prepared for splicing, and the splicing itself should begin shortly.

November 15, 6:25PM – Repair crews at the site of the fiber cut report that multiple ducts were damaged and are currently being replaced.  One end of the cable has been prepped and is ready for splicing while preparation efforts remain ongoing on the opposite end.  The replacement cabling is expected to arrive on site at 6:45PM at which time it will be pulled through the duct to allow splicing to begin.

November 15, 4:25PM – Earlier today, a vertical boring contractor struck and cut one of the 864-strand fibers connecting Baltimore to the Internet exchange points in Northern Virginia. As a result, a great deal of data is currently routing over backup circuits, and congestion should be expected for the next 24 hours as crews work to replace the damaged fiber. We will post updates as reports arrive.