cancel
Showing results for 
Search instead for 
Did you mean: 

DNS/Routing issues for the last 36 hours

evilsooty999
Dabbler
Posts: 13
Thanks: 3
Registered: ‎14-07-2016

Re: DNS/Routing issues for the last 36 hours

Planetside 2 is working now for me so hopefully that's the end of it! Still on 51.6 IP address.

evilsooty999
Dabbler
Posts: 13
Thanks: 3
Registered: ‎14-07-2016

Re: DNS/Routing issues for the last 36 hours


@evilsooty999 wrote:

Planetside 2 is working now for me so hopefully that's the end of it! Still on 51.6 IP address.


Clearly spoke too soon...just kicked me out of the game and now can't log back in.

newagetraveller
Pro
Posts: 690
Thanks: 144
Fixes: 2
Registered: ‎03-08-2012

Re: DNS/Routing issues for the last 36 hours

Just got this message when checking my gateway. What does it mean? I had powered off my router for 30 min. then rebooted. Now on a 51.6 ip. Still the same problem.

"Custom diagnostic check on IP 51.6.xx.xx

Array
(
    [1] =>  7  core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24)  5.256 ms
)

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Update topic in the Community Announcements forum will help us to diagnose the problem.

  • core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.256 ms"
Riza
Rising Star
Posts: 110
Thanks: 7
Fixes: 1
Registered: ‎24-07-2014

Re: DNS/Routing issues for the last 36 hours

The gateway checker tool is outdated as most of us have been put on the new Plusnet network. However, our gateway/s not being detected on the checker as the checker hasn't been updated to figure out which gateway is which from a trace from our connection to the site.

I have reported this since I have been moved to the new gateway but everything's gone silent...

https://community.plus.net/t5/Fibre-Broadband/Gateway-Check-Issues/m-p/1347933#M41106

Gateway thread
nightstalk3r
Rising Star
Posts: 221
Thanks: 20
Registered: ‎11-08-2015

Re: DNS/Routing issues for the last 36 hours

Well it seem a workaround is a static IP, so Plusnet the ball is in your court and i suggest you roll out static IP's to those affected customers and refund those who have paid money to test this fix for you.

 

This [-Censored-]s been going on for almost a week now and you are still clueless about your own network, and you still haven't officially acknowledged the issue(official means posted on the service status page)

 

How did Plusnet get this bad, it used to be one of the best ISP's with the best customer service and in a short space of time its gone down the crapper and is now one of the worst.

 

You've got until the end of today or im leaving tomorrow.

All4One
Grafter
Posts: 289
Registered: ‎17-03-2013

Re: DNS/Routing issues for the last 36 hours

You heard him (nightstalk3r) Plusnet! Best fix that network issue by the end of the day or else he's back off to France tomorrow Cheesy

Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: DNS/Routing issues for the last 36 hours

https://community.plus.net/t5/Service-Status/Access-to-online-services-and-sites-NEW/m-p/1349539#M56

 

 

Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
nshallcross
Hooked
Posts: 5
Registered: ‎14-07-2016

Re: DNS/Routing issues for the last 36 hours

Thumbs_Up

Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: DNS/Routing issues for the last 36 hours

Well it seem a workaround is a static IP, so Plusnet the ball is in your court and i suggest you roll out static IP's to those affected customers and refund those who have paid money to test this fix for you.

Not really as all adding a static IP does is mask the problem. We're working to get the underlying cause resolved.

Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Ridley
Newbie
Posts: 3
Registered: ‎14-07-2016

Re: DNS/Routing issues for the last 36 hours

Hello I've just signed up to the forum, I'm having issues to can't even sign in on my Xbox and PlayStation for about 3 days due to the Dns. my public ip starts with 51.6 so I assume I'm one of the affected? It's really annoyed me thinking it had been on my end doing everything to fix it when it has been a providers problem and no reason to why it's happening.
Tsuanmi49
Grafter
Posts: 28
Registered: ‎12-07-2016

Re: DNS/Routing issues for the last 36 hours

Hi, I'd like to reiterate that I am on the 209.93 ip range and I have also been having these exact same problems since Friday the 8th of July. I found a work around was to use a public VPN. It does seem like it is a routing issue.

nightstalk3r
Rising Star
Posts: 221
Thanks: 20
Registered: ‎11-08-2015

Re: DNS/Routing issues for the last 36 hours


@Chris wrote:

Well it seem a workaround is a static IP, so Plusnet the ball is in your court and i suggest you roll out static IP's to those affected customers and refund those who have paid money to test this fix for you.

Not really as all adding a static IP does is mask the problem. We're working to get the underlying cause resolved.


 

So you are saying despite the fact there is now a known temporary workaround for this issue that your systems have caused you wont offer it to affected customers and you expect us to live with this for probably several more weeks?

Thats great customer care right there.

Anyone would think we werent paying customers paying for a service your failing to provide.

Shermo
Dabbler
Posts: 11
Thanks: 1
Registered: ‎12-07-2016

Re: DNS/Routing issues for the last 36 hours

Started when they started blocking more sites a few weeks ago this definitely isn't a new issue, has been pretty dire since in all honesty. VPN helps but nice to get full speed with low pings for gaming. With the latest price hikes incoming makes me wonder what we are paying for atm..
Tsuanmi49
Grafter
Posts: 28
Registered: ‎12-07-2016

Re: DNS/Routing issues for the last 36 hours

I agree. I VPN will let you browse all be it very slowly. But there is no way in hell you can game off it. Its incredibly slow. I looks like a routing issue, so I have no idea why Plus net are sending an open reach engineer to my place on Tuesday...

 

tracert vl.api.np.km.playstation.net

Tracing route to us-p1-np-regcam-2129210197.us-west-1.elb.amazonaws.com [54.183.39.181]
over a maximum of 30 hops:

  1     6 ms     1 ms     2 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     8 ms    10 ms     8 ms  be3-3106.psb-ir02.plus.net [195.166.143.140]
  5     9 ms    11 ms     9 ms  195.99.125.138
  6    10 ms     9 ms    11 ms  peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
  7    12 ms    24 ms     9 ms  t2c4-et-8-3-0-0.uk-lon1.eu.bt.net [166.49.211.250]
  8    10 ms    10 ms    12 ms  82.112.101.73
  9    10 ms    11 ms     9 ms  ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
 10    82 ms    84 ms    81 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
 11   173 ms   158 ms   148 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 12   148 ms   146 ms   146 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 13   163 ms   166 ms   162 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 14   170 ms   169 ms   169 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 15   163 ms   163 ms   163 ms  ae-4.r06.plalca01.us.bb.gin.ntt.net [129.250.4.118]
 16   168 ms   167 ms   167 ms  ae-1.amazon.plalca01.us.bb.gin.ntt.net [140.174.21.182]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   170 ms   169 ms   169 ms  72.21.222.220
 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.

tracert portal.plus.net

Tracing route to portal.plus.net [212.159.9.2]
over a maximum of 30 hops:

  1     3 ms     1 ms     4 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     9 ms  be3-3104.psb-ir01.plus.net [195.166.143.136]
  5     9 ms     8 ms    10 ms  gr-11-1-0.ptw-cr02.plus.net [195.166.129.189]
  6    10 ms     9 ms    10 ms  ae1.pcl-cr02.plus.net [195.166.129.3]
  7    11 ms    12 ms    10 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  8    10 ms     9 ms     9 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  9    16 ms     *       16 ms  84-93-224-48.plus.net [84.93.224.48]
 10     *        *        *     Request timed out.
 11    16 ms    15 ms    15 ms  10.104.128.53
 12    15 ms    17 ms    16 ms  portal.plus.net [212.159.9.2]

Trace complete.

tracert playstation.com

Tracing route to playstation.com [209.200.152.198]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     8 ms  be3-3106.psb-ir02.plus.net [195.166.143.140]
  5    11 ms     8 ms     8 ms  195.99.125.142
  6     9 ms     9 ms    11 ms  peer1-et-2-1-0.telehouse.ukcore.bt.net [62.172.103.25]
  7     *        *        *     Request timed out.
  8    10 ms    10 ms    11 ms  unknown.prolexic.com [72.52.60.192]
  9    11 ms    10 ms    10 ms  unknown.prolexic.com [72.52.60.199]
 10    11 ms     9 ms    10 ms  unknown.prolexic.com [209.200.152.198]

Trace complete.
gooner77
Grafter
Posts: 39
Thanks: 1
Registered: ‎22-09-2009

Re: DNS/Routing issues for the last 36 hours

I have been having PSN issues that seem to have been caused by this routing. Can you advise when this is going to be fixed as it has been going on since 8th July