site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
2648
Share Topic
Posting?
Post a:
Post a:
Links: ·Frontier Communications ·Broadband Tweaks ·Equipment Support ·Site Tools ·Frontier Page for Ex Verizon Customers
page: 1 · 2 · 3
AuthorAll Replies


DraidenGG

@frontiernet.net

reply to kjpwv

Re: This sucks Frontier inet is down

Router keeps kickin me , gotta reload pages half a dozen times to get anywhere ... Barbour County , WV here . highly perturbed --.--
Thing was fine all day till about 7 pm then this again . ugh


Intoxicoded

join:2011-05-02
USA
kudos:2

reply to gozer
I'm having the same. seen my speeds drop from 12 meg to 7 meg then i cant do a dang thing. Just joined frontier a few days ago, not good timing lol


jpgr
WAR

join:2011-08-18
Clyde, OH

Srry fellas they were instaling my new line that took the whole country down ! LOL



Hank
Searching for a new Frontier
Premium
join:2002-05-21
Burlington, WV
kudos:1

said by jpgr:

Srry fellas they were instaling my new line that took the whole country down ! LOL

I guess we'll forgive you or eventually forget.


NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:9
Reviews:
·SONIC.NET
·Pacific Bell - SBC

reply to gozer

said by gozer:

Yes I can now get some sites like here, but look at this tracert to RIT here it looks like its TW that is down.

I don't think your trace is indicative of the problem:
Tracing route to rit.edu [129.21.1.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     1 ms  homeportal [192.168.42.1]
  2    42 ms    25 ms    25 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    24 ms    24 ms    24 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    24 ms    24 ms    24 ms  0.xe-7-1-0.gw.pao1.sonic.net [69.12.211.5]
  5    26 ms    25 ms    25 ms  0.xe-6-1-0.gw2.200p-sf.sonic.net [64.142.0.109]
  6    26 ms    26 ms    26 ms  as0.gw.200p-sf.sonic.net [208.106.96.249]
  7    26 ms    26 ms    26 ms  xe-10-1-0.bar2.SanFrancisco1.Level3.net [4.53.134.9]
  8    25 ms    25 ms    26 ms  ae-6-6.ebr2.SanJose1.Level3.net [4.69.140.154]
  9    26 ms    36 ms    49 ms  ae-72-72.csw2.SanJose1.Level3.net [4.69.153.22]
 10    27 ms    26 ms    26 ms  ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
 11    95 ms    93 ms    94 ms  ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
 12   103 ms   102 ms   102 ms  ae-4-4.car2.Buffalo1.Level3.net [4.69.140.241]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 
Trace complete.
 
Not saying that there is no problem, but a trace route to 'rit.edu' from outside of Frontier is also timing out, so it is likely that this particular destination is refusing to respond to diagnostic packets.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:22
Reviews:
·Verizon Online DSL
·Frontier Communi..

I can confirm the above about RIT. Try their mirror server instead. That pings!

Tracing route to thwomp.rc.rit.edu [129.21.171.98]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.3.1
2 15 ms 18 ms 14 ms 10.41.15.1
3 6 ms 8 ms 8 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4 23 ms 26 ms 23 ms so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
5 47 ms 34 ms 30 ms 0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
6 33 ms 30 ms 25 ms 0.xe-8-1-0.XL1.IAD8.ALTER.NET [152.63.32.50]
7 54 ms 27 ms 27 ms 0.xe-10-1-0.GW12.IAD8.ALTER.NET [152.63.35.102]
8 26 ms 25 ms 28 ms twtelecom-gw.customer.alter.net [152.179.50.186]
9 62 ms 51 ms 51 ms roc1-ar3-xe-2-0-0-0.us.twtelecom.net [66.192.253.110]
10 57 ms 54 ms 56 ms 64-128-122-22.static.twtelecom.net [64.128.122.22]
11 51 ms 51 ms 51 ms rit-core2-pp-rit2-vlan2812.rit.edu [129.21.8.45]
12 51 ms 51 ms 51 ms thwomp.rc.rit.edu [129.21.171.98]

Trace complete.


gozer
Premium
join:2010-08-09
Rochester, NY

I traced allso and yes the primary dns name times out can't remeber if I ever did trace or ping from cmd window to rit.edu but I did use it in a trace programm awhile ago several months and it did allways respond then. Anyway we all now know that the outage was big and affected alot of people in diferent ways.


Saturday, 25-May 11:55:26 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics