Losing connection

[jules52350]

Once the turn my actiontec router on , for the last 12 hours it has taken about 10 minutes for the dsl and internet lights to turn to solid, then i am able to get on the internet but it disconnects within 20 minutes and the dsl lights blinks and the internet lights goes dark. When i was able to access the internet my speed was horrible with download speed about 1.0 and upload speed 0.39.  I have also spoken to coworkers who have verizon and say they experienced the same thing yesterday, Cistomer service says there is no outage in the md/dc area however i find it strange several people are experiencing the same issue.  Has anyone else in the md/dc eperience any issues within the last 24 hours  

[dslr595148]

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up.  It might shown up as the final hop (bottom-most line of the trace)  might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I saw when I was using Verizon

---

news.giganews.com

    traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
    2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
    3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
    4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
    5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
    6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms
 

---

Step two: Can you provide the Transceiver Statistics from your modem?

#3 If you don't know how to get that info:

a) What is the brand and model of your modem?

b) If you have a RJ-45 WAN port router connected to it: What is the brand and model of the RJ-45 WAN port router?

#4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?

[jules52350]

Thank you, will get that information as soon as i get home, I dont know if it helps or not, but i tried it with a different modem and experience the exact same issue.

[jules52350]

Hello, got home yesterday and it seems everything is working well, getting better speeds, called customer service and ask did the network people do anything externally, they said no, however it magically is back to normal  i did run the report and received below data

 traceroute to 71.178.98.5 (71.178.98.5), 30 hops max, 60 byte packets

1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 2 ms 2 ms 2 ms
3 ash-b2-link.telia.net (213.155.130.91) 0 ms 0 ms ash-b2-link.se.telia.net (80.91.245.225) 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 10 ms 1 ms 1 ms
5 B300.WASHDC-LCR-21.verizon-gni.net (130.81.209.207) 5 ms 5 ms 5 ms
6 G2-0.WASHDC-CHCHMDBE-ERXG12.verizon-gni.net (130.81.197.73) 5 ms 5 ms 5 ms
7 pool-71-178-98-5.washdc.east.verizon.net (71.178.98.5) 33 ms 36 ms 38 ms

news-europe.giganews.com

traceroute to 71.178.98.5 (71.178.98.5), 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 41 ms 41 ms 41 ms
2 te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 0 ms 0 ms te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms
3 te0-7-0-25.mpd22.ams03.atlas.cogentco.com (154.54.36.214) 0 ms te0-0-0-1.ccr21.ams03.atlas.cogentco.com (130.117.0.81) 0 ms te0-3-0-4.mpd22.ams03.atlas.cogentco.com (130.117.3.21) 0 ms
4 be2275.ccr21.lon13.atlas.cogentco.com (130.117.51.253) 8 ms be2184.ccr21.lpl01.atlas.cogentco.com (154.54.37.70) 10 ms be2288.mpd22.lon13.atlas.cogentco.com (154.54.62.149) 8 ms
5 te0-2-0-3.ccr22.bos01.atlas.cogentco.com (154.54.0.209) 76 ms te0-7-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.169) 75 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com (154.54.1.93) 78 ms
6 be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 86 ms be2094.ccr21.jfk02.atlas.cogentco.com (154.54.30.13) 82 ms be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 84 ms
7 be2151.mpd22.dca01.atlas.cogentco.com (154.54.40.73) 88 ms be2113.ccr41.iad02.atlas.cogentco.com (154.54.6.169) 88 ms be2151.mpd22.dca01.atlas.cogentco.com (154.54.40.73) 88 ms
8 be2113.ccr41.iad02.atlas.cogentco.com (154.54.6.169) 89 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 96 ms be2112.ccr41.iad02.atlas.cogentco.com (154.54.5.233) 89 ms
9 B300.WASHDC-LCR-21.verizon-gni.net (130.81.209.207) 95 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 91 ms B400.WASHDC-LCR-22.verizon-gni.net (130.81.199.147) 92 ms
10 B300.WASHDC-LCR-21.verizon-gni.net (130.81.209.207) 94 ms P0-7-0-0.WASHDC-LCR-21.verizon-gni.net (130.81.151.231) 93 ms G4-0.WASHDC-CHCHMDBE-ERXG12.verizon-gni.net (130.81.197.75) 97 ms
11 pool-71-178-98-5.washdc.east.verizon.net (71.178.98.5) 113 ms G2-0.WASHDC-CHCHMDBE-ERXG12.verizon-gni.net (130.81.197.73) 89 ms G4-0.WASHDC-CHCHMDBE-ERXG12.verizon-gni.net (130.81.197.75) 91 ms