dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
861

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

1 edit

SeattleMatt

Premium Member

[Networking] Can't Access DSL Reports via FIOS

I haven't been able to access DSLR via my FIOS connection since early this morning.

Trace routes time out 4 hops in in Philly. Anyone else in DE/PA seeing this?

Hopped on my neighbor's wireless - she's also on FIOS - same thing. So, definitely not my personal connection.....
sam64
join:2006-07-31
Newtown, PA

sam64

Member

Was seeing the same situation this morning. Had similar situations with other websites - time.com, washingtonpost.com and others. Each time the trace routes timed out after 4 to 6 hops. Finally connected into my work VPN and was able to access all the sites.

Methinks FIOS is having some sort of DNS issue

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

Hah! Yeah, i'm actually on my work's VPN right now...

My trace dies at 130.81.199.20... so yeah, definitely a resolution issue somewhere...

sivran
Vive Vivaldi
Premium Member
join:2003-09-15
Irving, TX

sivran

Premium Member

If it were a name resolution issue, your trace wouldn't even start.

K3SGM
- -... ...- -
Premium Member
join:2006-01-17
Columbia, PA

K3SGM to SeattleMatt

Premium Member

to SeattleMatt
I can't access DSLR via Fios, I'm using my Comcast line to post this...

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

KA3-
Thanks for the confirm. Looks like it's definitely a regional issue.

sashwa
Mod
join:2001-01-29
Alcatraz

sashwa to SeattleMatt

Mod

to SeattleMatt
Can any of you not able to access DSLR via FiOS, get here if you use a proxy?
ScrawnyB
join:2004-05-18
Mechanicsburg, PA

ScrawnyB to SeattleMatt

Member

to SeattleMatt
said by SeattleMatt:

Trace routes time out 4 hops in in Philly. Anyone else in DE/PA seeing this?

I'm hitting the page fine on FiOS from the Harrisburg, PA area.

using these DNS servers...
71.250.0.14nsnwrk02.verizon.net.
71.252.0.14nsrest02.verizon.net.
71.243.0.14nsbost02.verizon.net.
 

Trace Route:
traceroute to www.dslreports.com (64.91.255.98), 30 hops max, 60 byte packets
 1  FIOSWAN (10.0.0.1)  0.249 ms  0.189 ms  0.192 ms
 2  L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1)  6.006 ms  6.295 ms  6.708 ms
 3  G0-2-1-5.HRBGPA-LCR-22.verizon-gni.net (100.41.198.150)  5.894 ms  5.791 ms  5.684 ms
 4  ae16-0.RES-BB-RTR2.verizon-gni.net (130.81.163.98)  17.622 ms  35.906 ms  35.803 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  0.ae2.XL4.CHI13.ALTER.NET (140.222.225.191)  49.915 ms  49.816 ms  49.622 ms
10  TenGigE0-7-0-1.GW5.CHI13.ALTER.NET (152.63.66.202)  46.127 ms  47.498 ms TenGigE0-5-0-2.GW5.CHI13.ALTER.NET (152.63.70.17)  38.752 ms
11  giglinx-gw.customer.alter.net (152.179.92.62)  99.741 ms  99.642 ms  61.051 ms
12  lw-dc2-core6-te9-2.rtr.liquidweb.com (209.59.157.226)  43.220 ms  43.310 ms  43.475 ms
13  lw-dc3-dist15.rtr.liquidweb.com (69.167.128.205)  44.633 ms  45.092 ms  43.750 ms
14  www.dslreports.com (64.91.255.98)  44.037 ms  44.056 ms  44.177 ms
 
dewdude
pfSense on xcp-ng Asterisk geek
join:2010-03-27
Manassas, VA
·voip.ms
(Software) pfSense
(Software) DD-WRT

dewdude to SeattleMatt

Member

to SeattleMatt
Haven't had an issue at all today from Northern Virginia. I don't remember what DNS I'm using; I think a combo of Vz and Google.

Tracing route to www.dslreports.com [64.91.255.98]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     3 ms     3 ms  L100.WASHDC-VFTTP-62.verizon-gni.net [96.231.212.1]
  3     5 ms     7 ms     6 ms  G0-8-3-3.WASHDC-LCR-22.verizon-gni.net [130.81.182.230]
  4    81 ms    25 ms    45 ms  so-14-0-0-0.RES-BB-RTR2.verizon-gni.net [130.81.22.56]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    29 ms    28 ms    40 ms  0.ae2.XL4.CHI13.ALTER.NET [140.222.225.191]
 10    31 ms    27 ms    30 ms  TenGigE0-5-0-3.GW5.CHI13.ALTER.NET [152.63.70.21]
 11   367 ms   224 ms    79 ms  giglinx-gw.customer.alter.net [152.179.92.62]
 12    35 ms    32 ms    33 ms  lw-dc2-core6-te9-2.rtr.liquidweb.com [209.59.157.226]
 13    36 ms    34 ms    36 ms  lw-dc3-dist15.rtr.liquidweb.com [69.167.128.205]
 14    36 ms    37 ms    38 ms  www.dslreports.com [64.91.255.98]
 

Thinkdiff
MVM,
join:2001-08-07
Bronx, NY

Thinkdiff to SeattleMatt

MVM,

to SeattleMatt
DSLR only has a single IP address and routing does not use DNS, so that's kind of a moot point. DNS is an end-user service.

Simply a routing problem, and VZ is likely aware already. Although it couldn't hurt to post traceroutes to effected sites in the Direct forum. Maybe they can pass it up the chain to get a faster resolution.

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

1 edit

SeattleMatt

Premium Member

Well,
We're now on almost 24 hrs and still can't reach DSLR - still using my work's VPN connection to post this. I'll put something in Direct.

If I do a trace - it eventually makes it to the last Liquidweb.com hop - but then dies before making it to dslreports. Plus, throw in about 7 timeout lines after the core router hop I mentioned in Philly.

Swingerhead
Premium Member
join:2004-04-06
Richmond, VA

Swingerhead to SeattleMatt

Premium Member

to SeattleMatt
FIOS in Virginia, accessing just fine.
sam64
join:2006-07-31
Newtown, PA

sam64 to SeattleMatt

Member

to SeattleMatt
Same issue here. The tracert does eventually make it to Liquidweb.com and then dslreports after about 7 timeout lines. Definitely a routing issue with FIOS because once again I can access thru my work VPN.

@JeepMatt - did you put something into the Direct Forum?
swope1221
join:2008-08-26
Newtown, PA

swope1221 to SeattleMatt

Member

to SeattleMatt
Hi Jeep, I had a similar issue a while back. See: »unable to access dslreports on home network
It eventually resolved itself, but it took a couple of days.

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

Sam-
I did open in Direct. But feel free to add your own. So far I'm just going through front line steps.

Swope - yep, same experience

tito79
join:2010-03-14
Port Saint Lucie, FL

tito79

Member

Heart bleed effecting thousands of people on the internet they said internet will be very slow and many web pages will not be accessible.

SparkChaser
Premium Member
join:2000-06-06
Downingtown, PA

SparkChaser to SeattleMatt

Premium Member

to SeattleMatt
Okay abour 25 mi north of you



SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt to tito79

Premium Member

to tito79
Is anyone else still having issues near Wilmington / West Chester? In the office today - Direct forum is saying technicians see no issues.
SeattleMatt

SeattleMatt

Premium Member

Finally back home. Still no access.

This is eff'd up. I'm actually curious to see what is causing this.

Rattler
join:2001-04-13
Havertown, PA

Rattler

Member

said by SeattleMatt:

Finally back home. Still no access.

This is eff'd up. I'm actually curious to see what is causing this.

No problems here in the immediate western 'burbs of Philthydelpia...

K3SGM
- -... ...- -
Premium Member
join:2006-01-17
Columbia, PA

K3SGM to SeattleMatt

Premium Member

to SeattleMatt
Jeep, whatever the problem was yesterday, it's now fixed up here in West Chester.

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

C'mon KA3?
Why does every weird thing happen to just me! LOL.

Great - now I have no backup. Hahhah. Direct forum is investigating for me.
SeattleMatt

SeattleMatt

Premium Member

Ok - did some more digging. Yesterday I couldn't hit the site on my system or my neighbors.

So, just hopped over on to my neighbors' FIOS wifi (we're good friends) - her system will now bring up the site - however she's on a 173.x.x.x IP - and i'm on a 71.x.x.x block. Our trace routes to DSLR show that the 4th hop is the only difference in our trace.

I go through 130.81.199.20 and can't reach it.
Her 4th hop is 130.81.209.186 and I can reach the site.

Our 1st two hops are the same - and to the same gateway.

Looks like that router in Philly is the culprit and part of some strange routing issue.
swope1221
join:2008-08-26
Newtown, PA

swope1221

Member

Sorry to hear your troubles still Jeep. I went back and checked my old thread I linked above, my ip addy started in the 64.x.x.x block back then. It literally took about a week to clear up, but I also didn't report it.

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

Swope-
Thanks man. Your thread was almost identical to mine.

Still can't reach it as of this morning.
SeattleMatt

2 edits

2 recommendations

SeattleMatt

Premium Member

Based on what I found last night, I had to wait for everyone to be off the net' this morning - Released the IP on the Actiontec - and restarted.

Now have an IP in the 173.49.x.x block and i'm back in business.

Very odd behavior...but, oh well.. 1 thing I did notice wast that some location apps were showing me being in Media, PA with the 71 IP, and now i'm back in Wilmington.

Phew! I couldn't handle living in Delco... hahahha...
dewdude
pfSense on xcp-ng Asterisk geek
join:2010-03-27
Manassas, VA
·voip.ms
(Software) pfSense
(Software) DD-WRT

dewdude to SeattleMatt

Member

to SeattleMatt
I'm wondering if there was an issue with some connectivity going up to that area. A friend of mine apparently had some issues trying to stream Slingbox, he lives outside of Boston. Connections were getting routed *through Chicago* to get there from my location in Northern Virginia.