Author Topic: Omni DNS issues?  (Read 4174 times)

0 Members and 1 Guest are viewing this topic.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55928
  • Rating: +3152/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Omni DNS issues?
« on: May 21, 2012, 01:50:24 pm »
I think there might be DNS issues or something with Omnimaga since the past few days, because about half of the pages I try to load will take between 8 seconds and 2 minutes, and in some occasions, they will load, but then hang, with some images missing for several seconds (like right now, the URL and Underline BBCode buttons are missing).

It might not be the server, because since this started, I only saw 3 high script load time results (2-3 seconds at bottom of page) and most other pages were generated under 1 seconds.

This issue seems to only affect a small range of ISPs, because when I checked isup.me when pages load slow, it said it was up for other people.  However, Omnimaga is the very only site where I have this problem happening and it's intermittent, meaning sometimes it's fine, while others it's not. Every other site loads perfectly.

I ran two different traceroutes, one from a website and the second one from Command prompt, 3 times each, and this is what I got:

Quote
23.21.59.101 is from United States(US) in region North America


TraceRoute to 23.21.59.101 [ec2-23-21-59-101.compute-1.amazonaws.com]

Hop   (ms)   (ms)   (ms)           IP Address   Host name
 1      0      0      0         8.9.232.73     xe-5-3-0.edge3.dallas1.level3.net 
 2      1      0      0         4.69.145.254     vlan90.csw4.dallas1.level3.net 
 3      0      0      0         4.69.151.170     ae-93-93.ebr3.dallas1.level3.net 
 4      20      21      20         4.69.134.22     ae-7-7.ebr3.atlanta2.level3.net 
 5      33      33      33         4.69.132.86     ae-2-2.ebr1.washington1.level3.net 
 6      33      40      33         4.69.134.142     ae-91-91.csw4.washington1.level3.net 
 7      33      33      33         4.69.149.205     ae-4-90.edge1.washington1.level3.net 
 8      42      43      42         4.28.51.94     amazon.com.edge1.washington1.level3.net 
 9      43      43      42         205.251.245.31      - 
 10      47      47      47         205.251.245.41      - 
 11      44      44      44         216.182.224.197      - 
 12      Timed out      Timed out      Timed out               - 
 13      Timed out      Timed out      Timed out               - 
 14      Timed out      Timed out      Timed out               - 
 15      Timed out      Timed out      Timed out               - 

Trace aborted.

Quote
Tracing route to omnimaga.org [23.21.59.101]
over a maximum of 30 hops:

  1     7 ms     1 ms     2 ms  192.168.0.1
  2    11 ms    10 ms    11 ms  10.85.88.1
  3    11 ms    11 ms    10 ms  10.170.161.114
  4    15 ms    14 ms    26 ms  216.113.123.158
  5    31 ms    30 ms    30 ms  216.113.123.174
  6    40 ms    29 ms    27 ms  equinix02-iad2.amazon.com [206.223.115.35]
  7    32 ms    30 ms    29 ms  72.21.220.47
  8    28 ms    27 ms    30 ms  72.21.222.155
  9   764 ms     *      753 ms  216.182.224.91
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

It seems to hang at different places in both cases. There seems to be problems with 216.182.224.197, though, which is an Amazon IP ( http://www.whoisstuff.net/ip-lookup.php?domain=216.182.224.197 ). Basically I think something might be blocking Omnimaga between where it's hosted and my ISP, but it seems to be on Amazon's side rather than mine.
« Last Edit: May 21, 2012, 01:51:28 pm by DJ_O »