Vault › General › DDO-Specific Discussion › Problem staying connected in the evenings.
(Moderator: Strakeln)
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Problem staying connected in the evenings. (Read 4120 times)
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Problem staying connected in the evenings.
Feb 22nd, 2016 at 5:26am
Print Post  
Hey guys,

Over the last week and a half I have been getting disconnect, around the same time every evening.

Other games and websites work fine, including lamannia.

Here is the TRACERT report.

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

  1    38 ms    38 ms    38 ms  rdl803.ba.optusnet.com.au [198.142.130.29]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    51 ms    51 ms    51 ms  198.142.250.229
  5    49 ms    49 ms    48 ms  198.142.139.116
  6    61 ms    51 ms    75 ms  198.142.139.132
  7   227 ms   257 ms   228 ms  203.208.192.205
  8   248 ms   253 ms   221 ms  203.208.182.158
  9   231 ms   227 ms   222 ms  203.208.173.138
10   231 ms   229 ms   227 ms  206.111.12.77.ptr.us.xo.net [206.111.12.77]
11   318 ms   314 ms   316 ms  207.88.13.233.ptr.us.xo.net [207.88.13.233]
12   317 ms   311 ms   313 ms  207.88.12.117.ptr.us.xo.net [207.88.12.117]
13   324 ms   320 ms   319 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
14   354 ms   323 ms   329 ms  te-4-1-0.rar3.miami-fl.us.xo.net [207.88.12.161]
15   329 ms   324 ms   320 ms  207.88.12.144.ptr.us.xo.net [207.88.12.144]
16   320 ms   345 ms   314 ms  207.88.12.190.ptr.us.xo.net [207.88.12.190]
17   322 ms   319 ms   318 ms  207.88.12.123.ptr.us.xo.net [207.88.12.123]
18   320 ms   320 ms   318 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21]
19   337 ms   345 ms   324 ms  ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
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.

Can anyone help me out with this?
  
Back to top
 
IP Logged
 
Alex DeLarge
Epic Poster
*****
Offline


Get ready for some of
the 'ol in-out, in-out

Posts: 3481
Location: Foggy Albion
Joined: May 11th, 2013
Gender: Male
Re: Problem staying connected in the evenings.
Reply #1 - Feb 22nd, 2016 at 6:53am
Print Post  
IBtF (In before the Flav)  Grin Grin Grin
  
Back to top
 
IP Logged
 
Flav
Vault Frog
*
Offline


One Frog to Rule them
All!

Posts: 9984
Location: Land of the Frogs
Joined: Aug 29th, 2010
Gender: Male
Re: Problem staying connected in the evenings.
Reply #2 - Feb 22nd, 2016 at 7:01am
Print Post  
Looks like you have a network issue... in Cambridge, MA.

Now you start from Oz ( the .au is a dead giveaway ).
then you go to Singapore through Singtel backbone :
Code
Select All
inetnum:	203.208.192.0 - 203.208.223.255
netname:	SINGTEL-IX
descr:	SingTel Internet Exchange


That's probably where you move to XOXO :

Code
Select All
NetRange:	206.111.0.0 - 206.111.255.255
CIDR:	206.111.0.0/16
NetName:	XOXO-BLK-1


At hop 14, you're in Miami, Fl.
At hop 18, you're in Chicago, Il.

Can you try a tracert to Lamania, it's weird because the web server, the GLS servers, the game servers are all on the same network... and from your traceroute
that whole network should be unreachable.

Code
Select All
74.201.103.121  ddo.com
74.201.102.19  ns1.dns.turbine.com
74.201.102.19  dns.turbine.com
74.201.102.11  patch.ddo.com                              # Patch Server
74.201.102.11  patch-lm.ddo.com                              # Lamannia Patch Server
74.201.102.13  gls.ddo.com                                    # Game Server
74.201.102.13  gls-auth.ddo.com                              # Login Server
74.201.102.13  gls-lm.ddo.com                              # Lamannia Game Server
74.201.102.13  gls-auth-lm.ddo.com                        # Lamannia Login Server
74.201.102.42  forums.ddo.com                              # Forums
74.201.103.43  www.ddo.com                                    # Website

74.201.106.53 Wayfinder [DE]
74.201.106.64 Ghallanda
74.201.106.56 Argonnessen
74.201.106.21 Thelanis
74.201.106.22 Sarlona
74.201.106.23 Khyber
74.201.106.59 Cannith
74.201.106.60 Orien

  
Yes my avatar is an Hermine eating a Greenland Lemming for brunch.
Back to top
 
IP Logged
 
Flav
Vault Frog
*
Offline


One Frog to Rule them
All!

Posts: 9984
Location: Land of the Frogs
Joined: Aug 29th, 2010
Gender: Male
Re: Problem staying connected in the evenings.
Reply #3 - Feb 22nd, 2016 at 7:08am
Print Post  
Alex DeLarge wrote on Feb 22nd, 2016 at 6:53am:
IBtF (In before the Flav)  Grin Grin Grin


that's because I was busy answering ( and following a conference call about setting up a few VPNs between Sweden and France... yes the encrypted ones the NSA hates )
  
Yes my avatar is an Hermine eating a Greenland Lemming for brunch.
Back to top
 
IP Logged
 
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Re: Problem staying connected in the evenings.
Reply #4 - Feb 22nd, 2016 at 8:12am
Print Post  
Will Trace the Lamannia server tomorrow night, just logged back on again (11pm) and it seems to be running fine.
  
Back to top
 
IP Logged
 
Durk
The Deranged
*
Offline


I've got a secret!

Posts: 705
Location: The Harbor
Joined: May 15th, 2012
Gender: Male
Re: Problem staying connected in the evenings.
Reply #5 - Feb 22nd, 2016 at 1:56pm
Print Post  
@Flav;

I think Lamma moved to new servers recently. The client connects to an IP as a host now instead of gls-lm.
  
Back to top
 
IP Logged
 
Flav
Vault Frog
*
Offline


One Frog to Rule them
All!

Posts: 9984
Location: Land of the Frogs
Joined: Aug 29th, 2010
Gender: Male
Re: Problem staying connected in the evenings.
Reply #6 - Feb 22nd, 2016 at 2:40pm
Print Post  
yeah, I know, I was a bit busy at work today ( with a VPN that doesn't want to work ), I don't remember where I put my list of Turbine IPs, so I had to search it on the forums...

The ones I pulled out is probably outdated. but they are in Turbine's network, from the traceroute it seems the issue is before even reaching Boston.
( it's weird to see Oz going to Singapore, then to Miami to reach Boston, but well... Internet )

I need to update the list. but I just don't have the time right now.
I know I posted them all at some point here in The Vault, but the search is so shitty that I couldn't find it back.



  
Yes my avatar is an Hermine eating a Greenland Lemming for brunch.
Back to top
 
IP Logged
 
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Re: Problem staying connected in the evenings.
Reply #7 - Feb 23rd, 2016 at 5:43am
Print Post  
NOTE:  I can get the the log in screen and the Lamannia server is CLOSED screen.  However on the main log in server it sits at Installing pre-reqs

Okay so here is tonight's Trace results, firstly gls.ddo.com

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

  1    35 ms    35 ms    35 ms  rdl803.ba.optusnet.com.au [198.142.130.29]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    48 ms    48 ms    49 ms  211.29.125.193
  5    47 ms    47 ms    46 ms  198.142.139.116
  6    49 ms    47 ms    46 ms  198.142.139.132
  7   245 ms   249 ms   249 ms  203.208.174.189
  8   257 ms   254 ms   256 ms  203.208.149.249
  9   259 ms   261 ms   259 ms  203.208.173.138
10   261 ms   263 ms   260 ms  206.111.12.77.ptr.us.xo.net [206.111.12.77]
11   337 ms   344 ms   339 ms  207.88.13.233.ptr.us.xo.net [207.88.13.233]
12   349 ms   342 ms   345 ms  207.88.12.117.ptr.us.xo.net [207.88.12.117]
13   333 ms   336 ms   339 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
14   340 ms   344 ms   345 ms  te-4-1-0.rar3.miami-fl.us.xo.net [207.88.12.161]
15   333 ms   334 ms   332 ms  207.88.12.144.ptr.us.xo.net [207.88.12.144]
16   342 ms   345 ms   343 ms  207.88.12.190.ptr.us.xo.net [207.88.12.190]
17   346 ms   335 ms   338 ms  207.88.12.123.ptr.us.xo.net [207.88.12.123]
18   333 ms   336 ms   340 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21]
19   340 ms   341 ms   347 ms  ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
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.

Unfortunately Lammania is Closed, so I can't do a trace on it tonight Sad.

Here is the TRACE for www.ddo.com:

Tracing route to newwebvip.ddo.com [74.201.103.121]
over a maximum of 30 hops:

  1    34 ms    35 ms    34 ms  rdl803.ba.optusnet.com.au [198.142.130.29]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    49 ms    49 ms    49 ms  198.142.250.245
  7    49 ms    49 ms    49 ms  198.142.139.116
  8    50 ms    49 ms    49 ms  198.142.139.132
  9   420 ms   251 ms   251 ms  203.208.192.205
10   257 ms   261 ms   266 ms  203.208.182.158
11   259 ms   258 ms   257 ms  203.208.173.138
12   263 ms   265 ms   265 ms  206.111.12.77.ptr.us.xo.net [206.111.12.77]
13   339 ms   339 ms   347 ms  207.88.13.233.ptr.us.xo.net [207.88.13.233]
14   347 ms   339 ms   343 ms  207.88.12.117.ptr.us.xo.net [207.88.12.117]
15     *      346 ms   347 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
16   354 ms   346 ms   349 ms  te-4-1-0.rar3.miami-fl.us.xo.net [207.88.12.161]
17   337 ms   383 ms   347 ms  207.88.12.144.ptr.us.xo.net [207.88.12.144]
18   344 ms   339 ms   342 ms  207.88.12.190.ptr.us.xo.net [207.88.12.190]
19   352 ms   349 ms   344 ms  207.88.12.123.ptr.us.xo.net [207.88.12.123]
20   340 ms   344 ms   343 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21]
21   335 ms   337 ms   342 ms  ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
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.

Ghallanda Trace:

Tracing route to 74.201.106.64 over a maximum of 30 hops

  1    35 ms    35 ms    35 ms  rdl803.ba.optusnet.com.au [198.142.130.29]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    49 ms    49 ms    49 ms  198.142.250.253
  7    49 ms    49 ms    49 ms  198.142.139.116
  8    49 ms    49 ms    49 ms  198.142.139.132
  9   375 ms   256 ms   245 ms  203.208.131.205
10   252 ms   258 ms   252 ms  203.208.149.249
11   256 ms   258 ms   259 ms  203.208.173.138
12   241 ms   240 ms   245 ms  206.111.12.77.ptr.us.xo.net [206.111.12.77]
13   337 ms   341 ms   347 ms  207.88.13.233.ptr.us.xo.net [207.88.13.233]
14   337 ms   364 ms   343 ms  207.88.12.117.ptr.us.xo.net [207.88.12.117]
15   340 ms   334 ms   331 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
16   339 ms   341 ms   344 ms  te-4-1-0.rar3.miami-fl.us.xo.net [207.88.12.161]
17   339 ms   342 ms   342 ms  207.88.12.144.ptr.us.xo.net [207.88.12.144]
18   331 ms   332 ms   338 ms  207.88.12.190.ptr.us.xo.net [207.88.12.190]
19   338 ms   346 ms   336 ms  207.88.12.123.ptr.us.xo.net [207.88.12.123]
20   333 ms   345 ms   342 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21]
21   342 ms   350 ms   339 ms  ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
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.
« Last Edit: Feb 23rd, 2016 at 5:44am by Spiderpig »  
Back to top
 
IP Logged
 
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Re: Problem staying connected in the evenings.
Reply #8 - Feb 23rd, 2016 at 7:40am
Print Post  
I could reconnect at 10.30pm, I haven't restarted my modem or system.  Here is the Trace report:

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

  1    35 ms    35 ms    35 ms  rdl803.ba.optusnet.com.au [198.142.130.29]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    48 ms    48 ms    50 ms  211.29.125.193
  5    48 ms    47 ms    46 ms  198.142.139.116
  6    46 ms    46 ms    47 ms  198.142.139.132
  7   198 ms   308 ms   199 ms  203.208.174.189
  8   208 ms   219 ms   206 ms  203.208.149.249
  9   207 ms   206 ms   206 ms  203.208.173.138
10   209 ms   209 ms   210 ms  206.111.12.77.ptr.us.xo.net [206.111.12.77]
11   290 ms   294 ms   295 ms  207.88.13.233.ptr.us.xo.net [207.88.13.233]
12   294 ms   296 ms   294 ms  207.88.12.117.ptr.us.xo.net [207.88.12.117]
13   293 ms   304 ms   292 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
14   292 ms   293 ms   292 ms  te-4-1-0.rar3.miami-fl.us.xo.net [207.88.12.161]
15   292 ms   293 ms   296 ms  207.88.12.144.ptr.us.xo.net [207.88.12.144]
16   295 ms   294 ms   294 ms  207.88.12.190.ptr.us.xo.net [207.88.12.190]
17   300 ms   292 ms   294 ms  207.88.12.123.ptr.us.xo.net [207.88.12.123]
18   293 ms   294 ms   294 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21]
19   295 ms   294 ms   294 ms  ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
20   279 ms   278 ms   279 ms  209.117.103.10
21   274 ms   274 ms   274 ms  border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128.107]
22   279 ms   278 ms   278 ms  turbine-7.border1.bsn003.pnap.net [64.95.76.202]
23   276 ms   275 ms   276 ms  74.201.102.154
24   279 ms   280 ms   280 ms  74.201.102.13

Trace complete.
  
Back to top
 
IP Logged
 
Flav
Vault Frog
*
Offline


One Frog to Rule them
All!

Posts: 9984
Location: Land of the Frogs
Joined: Aug 29th, 2010
Gender: Male
Re: Problem staying connected in the evenings.
Reply #9 - Feb 23rd, 2016 at 1:40pm
Print Post  
Ok, now I know what happens and where it happens.

Basically the peering last hop in XOXO backbone gets saturated and there's not fallback route.
So packets gets dropped according to qos ( quality of service ) configuration...
Lets say that Game related stuff is low in the qos priority list.

When you have the issue the last responding router is ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
The next hop ( 209.117.103.10 ) also belongs to XOXO  :

Code
Select All
Net Range	209.116.0.0 - 209.119.255.255
CIDR	209.116.0.0/14
Name	ALGX-ABI-BLK14
Handle	NET-209-116-0-0-1


so it's a capacity issue in their backbone or a capacity issue between their backbone peer ( 209.117.103.10 )
and the PNAP one in Boston ( border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128.107] )

I wouldn't be surprised by the PNAP one, as the border1 router has a long history of being overloaded. ( you can dig some of them here in the Vault, if you manage to stroke the Vault Search Engine the fight way... )
Since PNAP is also the owner of the datacenter hosting DDO servers ( and not AC, AC2 and LoTRO now ) there's few chances your problem will be solved before they move DDO to the new Datacenter.

You're not going to spend $10000s on hardware to upgrade a peering router when you know the traffic on said router is going to decrease because a customer is going to leave you... I've seen that enough time to be able to qualify it as a certainty at work, as the answer to a few cases brought ot me was : Router overloaded, upgrade the controller card ( 2*$6K to latest Gen and the relevant line cards  ( $10K each ) to 10Gb. ( And that's for a PE [ read backbone border ] router not for a backbone router with Terabit interfaces and DWDM. ) ) Several time the customer answered back : some customers are moving out of that router, we will live with it for the few months needed for them to leave.
  
Yes my avatar is an Hermine eating a Greenland Lemming for brunch.
Back to top
 
IP Logged
 
[]
Madame President
******
Offline



Posts: 10532
Joined: Oct 16th, 2015
Re: Problem staying connected in the evenings.
Reply #10 - Feb 23rd, 2016 at 1:44pm
Print Post  
Flav literally cannot stop sucking Turbine's cock.
  
Back to top
 
IP Logged
 
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Re: Problem staying connected in the evenings.
Reply #11 - Feb 23rd, 2016 at 3:34pm
Print Post  
Oh well if that's the case then I guess no more DDO for a while.

Thanks for the help guys.
  
Back to top
 
IP Logged
 
KingLurker
Dragon Raider
***
Offline


I Love Drama!

Posts: 205
Location: Eveningstar
Joined: Mar 18th, 2014
Gender: Male
Re: Problem staying connected in the evenings.
Reply #12 - Feb 23rd, 2016 at 4:07pm
Print Post  
-_- what ...did he saY?
  
Back to top
 
IP Logged
 
Meat-Head
53%Moron57%Misunderstood
*
Offline


Why am I reading crap
on this forum?

Posts: 12345
Location: Oregon
Joined: Dec 5th, 2011
Gender: Male
Re: Problem staying connected in the evenings.
Reply #13 - Feb 23rd, 2016 at 8:10pm
Print Post  
Am I the only one who thought this is what OP needed: 10 Things Connected Couples Do
« Last Edit: Feb 23rd, 2016 at 8:11pm by Meat-Head »  
A half-dozen boss Vaulties donated generously with real money to my classroom during a fundraiser in May 2015 to get poor kids books to read. I won't forget that. They know who they are, and they freaking rule.

Disavowed wrote on Apr 19th, 2016 at 1:51pm:
Once you meat your personal goal you might want to give that some consideration.

Artorias wrote on Feb 10th, 2016 at 2:15pm:
Good grief Meat, you're hopeless. You would label the simple act of taking a shit as someone obeying the divine law of nature to leave a proof of existence.
Back to top
 
IP Logged
 
Spiderpig
Korthos Resident
*
Offline


No no no no no no no no
no ........ Well yes.

Posts: 36
Joined: Dec 10th, 2013
Re: Problem staying connected in the evenings.
Reply #14 - Feb 27th, 2016 at 6:21am
Print Post  
I had found a way around my connection problem, it worked for 1 day and now I get the "Failed to connect to patch server" error.

I can access the forum whilst using work around, but not the game.

Have No Proxy selected and tried the HOST file fix.  No Luck.

Please help.

NOTE:  Again it lasts for a couple of hours and then everything is okay again.

The Trace report to gls.ddo.com is fine.  Here is the patch server result:
Tracing route to patch.ddo.com [198.252.160.31]
over a maximum of 30 hops:

  1   247 ms   248 ms   251 ms  172.18.12.1
  2   250 ms   251 ms   253 ms  13.0d.39a9.ip4.static.sl-reverse.com [169.57.13.19]
  3   248 ms   247 ms   246 ms  ae12.dar01.mex01.networklayer.com [169.57.118.134]
  4   247 ms   248 ms   248 ms  ae8.bbr01.sr03.mex01.networklayer.com [50.97.19.104]
  5   297 ms   295 ms   299 ms  73.13.6132.ip4.static.sl-reverse.com [50.97.19.115]
  6   295 ms   294 ms   295 ms  ae7.bbr02.cs01.lax01.networklayer.com [173.192.18.167]
  7   301 ms   303 ms   302 ms  ae0.bbr02.eq01.sjc02.networklayer.com [173.192.18.150]
  8   302 ms   304 ms   302 ms  ae7.bbr01.eq01.sjc02.networklayer.com [173.192.18.164]
  9   303 ms   303 ms   303 ms  ae-10.r01.snjsca04.us.bb.gin.ntt.net [128.241.219.205]
10   303 ms   303 ms   305 ms  sjp-brdr-04.inet.qwest.net [63.146.27.213]
11   343 ms   358 ms   342 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
12   344 ms   347 ms   345 ms  206.103.215.50
13   341 ms   341 ms   340 ms  63.236.3.130
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.
« Last Edit: Feb 27th, 2016 at 6:36am by Spiderpig »  
Back to top
 
IP Logged
 
OnePercenter
Advocatus Diaboli
*
Offline


Ants Eat Dead Grasshoppers

Posts: 9985
Joined: Dec 4th, 2011
Gender: Male
Re: Problem staying connected in the evenings.
Reply #15 - Feb 27th, 2016 at 9:28am
Print Post  
Snowden is a Flav sock...
  
Feynman wrote on Jan 20th, 2015 at 4:57pm:
One thing for everyone who is a "skeptic" on this issue: Insurance companies are basing their underwriting on the assumption that it is real. They are refusing to write policies on homes that are likely to be in danger from rising seas 20 years from now, even though the resale rate of the homes is so high that they could keep writing policies for another 10 years and still not have to pay out on 1 policy in 5, but that would be irresponsible. Unethical, as well, but that's never stopped anyone before.


IMARANGER wrote on Jan 11th, 2014 at 6:12pm:
It is fairly natural to assume that the fair price for the pot is the fair value of the resources I needed to make the pot plus the fair value of my labor.

IMARANGER wrote on Jan 15th, 2014 at 4:56pm:
You were right this time, OnePercenter. 


iliveyourdream13 wrote on May 14th, 2014 at 2:02pm:
#bringbackreadingcomprehension
Back to top
 
IP Logged
 
Flav
Vault Frog
*
Offline


One Frog to Rule them
All!

Posts: 9984
Location: Land of the Frogs
Joined: Aug 29th, 2010
Gender: Male
Re: Problem staying connected in the evenings.
Reply #16 - Feb 28th, 2016 at 3:19pm
Print Post  
looks like the pnap peering again...

I know EWR is an IATA code for an airport... it should give you an idea of the area where it happens geographically.
  
Yes my avatar is an Hermine eating a Greenland Lemming for brunch.
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

Vault » Powered by YaBB 2.6.11!
YaBB Forum Software © 2000-2024. All Rights Reserved.

Valid RSS Valid XHTML Valid CSS Powered by Perl Source Forge