dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1092

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR

darcilicious

Premium Member

[Ziply] Can?t reach dslreports via Frontier connection

... but I can via cell (AT&T).

Anyone else in the area or am I just special?

OldNavyGuy
join:2018-07-24
Newberg, OR

1 recommendation

OldNavyGuy

Member

[Ziply] Re: Can?t reach dslreports via Frontier connection

You're special

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR

darcilicious

Premium Member

Right?

I can reach every other site just fine. Tried on multiple computers too.

OldNavyGuy
join:2018-07-24
Newberg, OR

OldNavyGuy

Member

I'm running a PingPlotter trace to dslreports.com and so far, the route is solid from here.
eprosenx
join:1999-09-05
Beaverton, OR

eprosenx to darcilicious

Member

to darcilicious
lol, where are you located?

Maybe it is a strategy to keep folks from posting mean things? (j/k)

OldNavyGuy
join:2018-07-24
Newberg, OR

OldNavyGuy to darcilicious

Member

to darcilicious
Try coming in on 64.91.255.98 instead of dslreports.com

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR

1 recommendation

darcilicious

Premium Member

That’s the IP address traceroute is resolving to already.
jwvo
join:2001-07-27
Seattle, WA

jwvo to OldNavyGuy

Member

to OldNavyGuy
looks ok from nearby, send a traceroute please.

traceroute to dslreports.com (64.91.255.98), 30 hops max, 60 byte packets
1 cr1-hlboornf-te-0-0-0-39.bb.as20055.net (204.194.220.20) 1.002 ms 0.963 ms 0.926 ms
2 cr2-hlboornf-be12.bb.as20055.net (107.191.236.24) 1.112 ms 1.084 ms 1.050 ms
3 cr2-ptldorpb-b-be12.bb.as20055.net (107.191.236.22) 1.182 ms 1.158 ms 1.125 ms
4 hu0-7-0-0.ccr21.pdx01.atlas.cogentco.com (38.104.105.145) 0.777 ms 0.779 ms 0.816 ms
5 be2671.ccr21.sea02.atlas.cogentco.com (154.54.31.77) 4.502 ms 11.064 ms be2670.ccr22.sea02.atlas.cogentco.com (154.54.42.149) 4.724 ms
6 154.54.89.102 (154.54.89.102) 24.607 ms be3284.ccr21.slc01.atlas.cogentco.com (154.54.44.74) 24.352 ms be2029.ccr32.slc01.atlas.cogentco.com (154.54.86.109) 24.629 ms
7 be3038.ccr22.den01.atlas.cogentco.com (154.54.42.98) 34.868 ms 34.655 ms 35.995 ms
8 be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 46.592 ms be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90) 46.284 ms be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 46.204 ms
9 be2831.ccr41.ord01.atlas.cogentco.com (154.54.42.166) 58.382 ms be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170) 58.443 ms 58.120 ms
10 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 58.534 ms 58.486 ms 58.431 ms
11 * * *
12 lw-dc3-core2.rtr.liquidweb.com (209.59.157.50) 80.071 ms 80.048 ms 80.045 ms
13 lw-dc3-storm1.rtr.liquidweb.com (69.167.128.141) 79.509 ms lw-dc3-storm2-po5.rtr.liquidweb.com (69.167.128.137) 80.269 ms lw-dc3-storm1.rtr.liquidweb.com (69.167.128.89) 78.621 ms
14 www.dslreports.com (64.91.255.98) 78.919 ms 78.900 ms 78.873 ms

OldNavyGuy
join:2018-07-24
Newberg, OR

OldNavyGuy to darcilicious

Member

to darcilicious
said by darcilicious:

That’s the IP address traceroute is resolving to already.

Correct.

I wanted to see if taking the DNS resolvers out of the equation made a difference.

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR
·Ziply Fiber

darcilicious

Premium Member

traceroute to www.dslreports.com (64.91.255.98), 64 hops max, 52 byte packets
1 fios_quantum_gateway (192.168.1.1) 3.224 ms 1.451 ms 1.338 ms
2 fdr01.frgv.or.nwestnet.net (50.46.181.57) 3.764 ms 4.072 ms 3.869 ms
3 50.46.176.86 (50.46.176.86) 5.466 ms 4.260 ms 9.046 ms
4 ae2---0.cor01.bvtn.or.nwestnet.net (50.46.176.0) 4.925 ms 4.983 ms 4.281 ms
5 ae0---0.cor02.bvtn.or.nwestnet.net (50.46.176.5) 4.999 ms 5.681 ms 4.842 ms
6 cr2-bvtnorxb-a-be100.bb.as20055.net (204.194.220.5) 5.528 ms 6.957 ms 5.439 ms
7 cr2-hlboornf-be11.bb.as20055.net (107.191.236.28) 6.325 ms 6.187 ms 7.215 ms
8 cr2-ptldorpb-b-be12.bb.as20055.net (107.191.236.22) 6.089 ms 6.791 ms 5.921 ms
9 hu0-7-0-0.ccr21.pdx01.atlas.cogentco.com (38.104.105.145) 5.861 ms 5.602 ms 5.460 ms
10 be2671.ccr21.sea02.atlas.cogentco.com (154.54.31.77) 9.588 ms
be2670.ccr22.sea02.atlas.cogentco.com (154.54.42.149) 9.935 ms 8.847 ms
11 154.54.89.102 (154.54.89.102) 31.160 ms 30.383 ms
be3284.ccr21.slc01.atlas.cogentco.com (154.54.44.74) 29.675 ms
12 be3038.ccr22.den01.atlas.cogentco.com (154.54.42.98) 40.769 ms 41.627 ms
be3037.ccr21.den01.atlas.cogentco.com (154.54.41.146) 40.022 ms
13 be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 228.472 ms 51.831 ms 51.792 ms
14 be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170) 65.051 ms 63.306 ms 179.360 ms
15 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 63.934 ms
be2765.ccr41.ord03.atlas.cogentco.com (154.54.45.18) 63.478 ms
be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 118.171 ms
16 * * *
17 lw-dc3-core1-eth2-19.rtr.liquidweb.com (209.59.157.244) 63.141 ms 62.771 ms 166.415 ms
18 lw-dc3-storm2.rtr.liquidweb.com (69.167.128.145) 64.078 ms
lw-dc3-storm1.rtr.liquidweb.com (69.167.128.89) 62.999 ms
lw-dc3-storm1.rtr.liquidweb.com (69.167.128.141) 63.398 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * *^C

OldNavyGuy
join:2018-07-24
Newberg, OR

OldNavyGuy

Member

Interesting.

lw-dc3-storm1.rtr.liquidweb.com (69.167.128.141) is the last hop before dslreports.com on my PingPlotter trace.

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR

darcilicious to OldNavyGuy

Premium Member

to OldNavyGuy
>> I wanted to see if taking the DNS resolvers out of the equation made a difference.

It doesn’t.

OldNavyGuy
join:2018-07-24
Newberg, OR

OldNavyGuy

Member

Check and see if your IP has been blacklisted -

»whatismyipaddress.com/bl ··· st-check

darcilicious
Cyber Librarian
Premium Member
join:2001-01-02
Forest Grove, OR

darcilicious

Premium Member

Only one listed:

! dnsbl.spfbl.net

OldNavyGuy
join:2018-07-24
Newberg, OR

2 edits

OldNavyGuy

Member

Same here and no issues.

So, I wonder if dslreports.com somehow blocked your IP.

There were issues with that in the past...some could reach DSLR, some couldn't.

»Cannot connect to site, from US through Firefox, Chrome, etc...
jwvo
join:2001-07-27
Seattle, WA

2 recommendations

jwvo

Member

it looks like filtering on the far end, thanks for posting the traceroute (i had picked a spot "close" to you but that one from you directly pretty much makes me think it is broken on the far end).

guppy_fish
Premium Member
join:2003-12-09
Palm Harbor, FL

1 recommendation

guppy_fish to darcilicious

Premium Member

to darcilicious
I have had DSLReprort ban my IP if I click on a button or link 2-3 times in a few seconds, some form of denial of service protection. I have a VPN I can fire up and get back on, so I know it is a IP Ban and then I have to take the router down for a few minutes to get a new WAN IP to access this site. Pain in the butt, so I have learned to wait on any UI actions with this site.

Smith6612
MVM
join:2008-02-01
North Tonawanda, NY

Smith6612

MVM

I haven't seen that behavior in quite some time. But I know the site, instead of banning my IP, would throw an HTTP code saying to slow down. And it would unblock me within 20-30 seconds.
BlitzenZeus
Burnt Out Cynic
Premium Member
join:2000-01-13

BlitzenZeus to darcilicious

Premium Member

to darcilicious
I'm relatively near you, but definitely not the same CO. Tonight I've been having problems with network routing dropping inconsistently to certain routes. It's been highly annoying actually. It will be fine for a few minutes, then be unreachable for a minute.
TJ_665
join:2001-07-04
Fairview, OR

TJ_665

Member

said by BlitzenZeus:

I'm relatively near you, but definitely not the same CO. Tonight I've been having problems with network routing dropping inconsistently to certain routes. It's been highly annoying actually. It will be fine for a few minutes, then be unreachable for a minute.

Been having weird network drop outs as well last couple of nights.
BlitzenZeus
Burnt Out Cynic
Premium Member
join:2000-01-13

BlitzenZeus

Premium Member

I started a new smokeping, and packetloss all over the place currently. I sure hope they didn't transition us to a network that can't handle the bandwidth.
ohnoobnet
join:2010-11-22

1 recommendation

ohnoobnet to darcilicious

Member

to darcilicious
It's been happening since a few days ago, intermitten packets loss every night. Something wrong with their network between hop 4 and 5. Maybe ddos attack or something causing the PL?

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 110 | 110 | 0 | 0 | 1 | 0 |
| fdr01.grhm.or.nwestnet.net - 0 | 110 | 110 | 2 | 3 | 30 | 8 |
| 50.46.176.78 - 0 | 110 | 110 | 4 | 5 | 22 | 4 |
| ae2---0.cor01.bvtn.or.nwestnet.net - 0 | 110 | 110 | 3 | 4 | 7 | 4 |
| ae0---0.cor02.bvtn.or.nwestnet.net - 77 | 26 | 6 | 506 | 506 | 506 | 506 |
| cr2-bvtnorxb-a-be100.bb.as20055.net - 88 | 24 | 3 | 0 | 506 | 507 | 507 |
| 107.191.236.64 - 80 | 25 | 5 | 0 | 35 | 36 | 35 |
| google-sttlwawb-b.pni.as20055.net - 69 | 29 | 9 | 0 | 110 | 130 | 130 |
| 108.170.245.97 - 77 | 26 | 6 | 42 | 87 | 120 | 120 |
| 74.125.253.61 - 72 | 28 | 8 | 0 | 34 | 37 | 35 |
| den03s10-in-f46.1e100.net - 84 | 25 | 4 | 0 | 509 | 510 | 509 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

OldNavyGuy
join:2018-07-24
Newberg, OR

2 edits

3 recommendations

OldNavyGuy

Member

The network issues this evening are totally different than the OP's issue of not being able to reach DSLR only.
ohnoobnet
join:2010-11-22

ohnoobnet

Member

Yes. I hit the wrong reply button. Was meant to reply to Blitzenzeus
Expand your moderator at work
jwvo
join:2001-07-27
Seattle, WA

1 recommendation

jwvo to ohnoobnet

Member

to ohnoobnet

[Ziply] Re: Can?t reach dslreports via Frontier connection

I am going to try to get some graphs for the cor01.bvtn - cor02.bvtn path to see what i can find out, my recollection though is that is actually a pretty large bundle (a bunch of hundred gig circuits) but we moved a lot of traffic flows to different paths over the last week and the feedback here says we have a lot of digging to do. I know for sure there is no congestion from cor02.bvtn towards the internet edge since i have that data directly.

We also saw some dos attacks last night toward a couple of fios users and actually made some tweaks to our filtering to be a bit more aggressive but those don't match up exactly with what is being reported here.
jwvo

jwvo

Member

If people are seeing issues in the northwest traceroutes are very very helpful to check in on things.
Outlet
join:2014-09-18

Outlet to jwvo

Member

to jwvo
I was having issues with Amazon video/twitch dropping out and buffering last evening, starting at around 8pm, not sure if that's related. It seems okay today and I was able to lessen the impact by VPNing to Seattle.

If it starts happening again, I'll try and figure out what server the video is coming from.
jwvo
join:2001-07-27
Seattle, WA

jwvo

Member

great, keep me posted. As you can tell, we want to be proactive and make sure everything works well.
lunadesign
join:2008-11-13
Beaverton, OR

1 recommendation

lunadesign to jwvo

Member

to jwvo
Was seeing significant issues last night on multiple routers in the NW last night and posted to the Frontier Direct forum. Here's what MTR looked like last night:

My traceroute [v0.85]
xxx (0.0.0.0) Thu Apr 23 22:48:01 2020
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.10.1 0.0% 142 0.2 0.2 0.2 0.3 0.0
2. fdr01.aloh.or.nwestnet.net 0.0% 142 1.6 2.5 0.9 22.8 3.0
3. 50.46.176.80 0.0% 142 2.1 2.8 1.3 23.6 2.5
4. ae2---0.cor01.bvtn.or.nwestnet.net 5.6% 142 2.3 2.9 1.6 17.3 1.4
5. ae0---0.cor02.bvtn.or.nwestnet.net 3.5% 142 2.1 2.4 1.4 6.5 0.6
6. cr2-bvtnorxb-a-be100.bb.as20055.net 9.2% 142 2.8 2.8 2.3 7.1 0.5
7. cr2-hlboornf-be11.bb.as20055.net 4.9% 142 3.4 3.3 2.8 3.8 0.0
8. cr2-ptldorpb-b-be12.bb.as20055.net 2.8% 142 3.2 3.5 3.1 4.0 0.0
9. hu0-7-0-0.ccr21.pdx01.atlas.cogentco.com 4.2% 142 3.2 3.1 2.5 3.6 0.0
10. be2670.ccr22.sea02.atlas.cogentco.com 2.8% 142 6.7 6.7 6.2 10.4 0.3
11. be2029.ccr32.slc01.atlas.cogentco.com 4.2% 142 26.6 35.5 26.6 93.9 19.0
12. be3038.ccr22.den01.atlas.cogentco.com 2.8% 142 37.3 37.2 36.7 50.0 1.0
13. be3036.ccr22.mci01.atlas.cogentco.com 7.0% 142 49.0 48.7 47.7 49.5 0.1
14. be2832.ccr42.ord01.atlas.cogentco.com 7.0% 142 60.4 60.4 60.0 60.9 0.0
15. be2766.ccr41.ord03.atlas.cogentco.com 3.5% 142 61.1 60.9 60.3 63.0 0.2
16. ???
17. lw-dc3-core2.rtr.liquidweb.com 6.4% 141 60.8 60.8 60.0 61.8 0.0
18. lw-dc3-storm2.rtr.liquidweb.com 3.5% 141 60.4 60.4 59.9 61.5 0.1
19. www.dslreports.com 5.7% 141 60.3 60.3 59.8 60.6 0.0

I'm used to seeing 1 or 2 hops with dropouts but not "all after host #3".

I haven't seen any problems so far this morning.