Page 2 of 2 FirstFirst 12
Results 41 to 80 of 80
  1. #41
    Join Date
    Nov 2011
    Location
    Internet
    Posts
    114
    Quote Originally Posted by kpmedia View Post
    I think there's a big difference between fair criticism (2+ hours) and whining (5 minutes). Plus I thought the purpose of the outage/updates forum is for awareness, not complaining/reviewing. If 5 minutes kills your business, get a dedicated HA cloud at a premium datacenter.

    .
    .
    I do not agree with you, the problem is not the server down for 5 minutes, the problem is that this has been repeated constantly.
      0 Not allowed!

  2. #42
    Join Date
    Oct 2009
    Posts
    36
    again, offline. works 3 hours and is offline for 5 minutes
      0 Not allowed!

  3. #43
    Join Date
    Jul 2006
    Location
    Australia
    Posts
    2,941
    Yeah I am down again also...
      0 Not allowed!

  4. #44
    Join Date
    Oct 2009
    Posts
    36
    servers back up
      0 Not allowed!

  5. #45
    Join Date
    Jul 2006
    Location
    Australia
    Posts
    2,941
    My server (network) keeps going up and down currently :/
      0 Not allowed!

  6. #46
    Join Date
    Feb 2006
    Location
    Kepler 62f
    Posts
    14,662
    I have 7 downtimes total from 3/31 to 4/3. The one that started this thread was about 1 hour, and attributed to errors one the network (not with any of the servers). The others were between 3 and 6 minutes long. That's likely a datacenter error, outside JPC's control. In fact, I tracedrt'd a VPS, in addition to JPC's own site, and each time the failure was at Total Server Solutions.

    Look at this fubar routing once it enters the datacenter:
    Code:
     12    46 ms     *       41 ms  67.199.136.189
     13    30 ms    33 ms    29 ms  abte2-1.10g.coloat.cust.atl01.mzima.net [67.199.136.182]
     14   132 ms   129 ms     *     te2-3.aa.atl.coloat.com [206.220.172.6]
     15    59 ms    41 ms    43 ms  ae1-213.atl11.ip4.tinet.net [173.241.130.53]
     16     *        *      140 ms  total-server-solutions-gw.ip4.tinet.net [173.241.130.54]
     17     *        *      122 ms  ae1-213.atl11.ip4.tinet.net [173.241.130.53]
     18     *        *        *     Request timed out.
     19   198 ms     *      204 ms  ae1-213.atl11.ip4.tinet.net [173.241.130.53]
     20     *        *      332 ms  total-server-solutions-gw.ip4.tinet.net [173.241.130.54]
     21     *        *        *     Request timed out.
     22     *        *      490 ms  total-server-solutions-gw.ip4.tinet.net [173.241.130.54]
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *      455 ms   439 ms  ae1-213.atl11.ip4.tinet.net [173.241.130.53]
     26  2719 ms     *       31 ms  static-X-X-X-X.nocdirect.com [X.X.X.X]
    This needs to be fixed, surely, but step off the JPC-sucks bus first.
    Place blame* where it belongs.

    * Even then, it can be hard to track down troublesome routers when the problem is intermittent.
    So it's still hard to "blame" anybody, assuming they're doing their jobs.


    .
    .
    Last edited by kpmedia; 04-03-2012 at 02:55 AM.
      0 Not allowed!

  7. #47
    Join Date
    Oct 2009
    Posts
    36
    tested with just-ping.com
    100% packet lost
    69.73.145.202


    Location Result min. rrt avg. rrt max. rrt IP
    Singapore, Singapore: Packets lost (100%) 69.73.145.202
    Amsterdam2, Netherlands: Packets lost (100%) 69.73.145.202
    Florida, U.S.A.: Packets lost (100%) 69.73.145.202
    Amsterdam3, Netherlands: Packets lost (100%) 69.73.145.202
    Hong Kong, China: Packets lost (100%) 69.73.145.202
    Sydney, Australia: Packets lost (100%) 69.73.145.202
    München, Germany: Packets lost (100%) 69.73.145.202
    Cologne, Germany: Packets lost (100%) 69.73.145.202
    New York, U.S.A.: Packets lost (100%) 69.73.145.202
    Stockholm, Sweden: Packets lost (100%) 69.73.145.202
    Santa Clara, U.S.A.: Packets lost (100%) 69.73.145.202
    Vancouver, Canada: Packets lost (100%) 69.73.145.202
    London, United Kingdom: Packets lost (100%) 69.73.145.202
    Madrid, Spain: Packets lost (100%) 69.73.145.202
    Padova, Italy: Packets lost (100%) 69.73.145.202
    Austin, U.S.A.: Packets lost (100%) 69.73.145.202
    Amsterdam, Netherlands: Packets lost (100%) 69.73.145.202
    Paris, France: Packets lost (100%) 69.73.145.202
    Shanghai, China: Packets lost (100%) 69.73.145.202
    Melbourne, Australia: Packets lost (100%) 69.73.145.202
    Copenhagen, Denmark: Checkpoint temporarily not available - - - -
    Lille, France: Packets lost (100%) 69.73.145.202
    San Francisco, U.S.A.: Packets lost (100%) 69.73.145.202
    Zurich, Switzerland: Packets lost (100%) 69.73.145.202
    Mumbai, India: Packets lost (100%) 69.73.145.202
    Chicago, U.S.A.: Packets lost (100%) 69.73.145.202
    Nagano, Japan: Packets lost (100%) 69.73.145.202
    Haifa, Israel: Packets lost (100%) 69.73.145.202
    Auckland, New Zealand: Packets lost (100%) 69.73.145.202
    Antwerp, Belgium: Packets lost (100%) 69.73.145.202
    Groningen, Netherlands: Packets lost (100%) 69.73.145.202
    Moscow, Russia: Packets lost (100%) 69.73.145.202
    Dublin, Ireland: Packets lost (100%) 69.73.145.202
    Oslo, Norway: Packets lost (100%) 69.73.145.202
    Kharkov, Ukraine: Packets lost (100%) 69.73.145.202
    Manchester, United Kingdom: Packets lost (100%) 69.73.145.202
    Vilnius, Lithuania: Packets lost (100%) 69.73.145.202
    Bucharest, Romania: Packets lost (100%) 69.73.145.202
    Bangkok, Thailand: Packets lost (100%) 69.73.145.202
    Kuala Lumpur, Malaysia: Packets lost (100%) 69.73.145.202
    Cape Town, South Africa: Packets lost (100%) 69.73.145.202
    Glasgow, United Kingdom: Packets lost (100%) 69.73.145.202
    Lisbon, Portugal: Packets lost (100%) 69.73.145.202
    Chicago, U.S.A.: Packets lost (100%) 69.73.145.202
    Dallas, U.S.A.: Packets lost (100%) 69.73.145.202
    Cairo, Egypt: Packets lost (100%) 69.73.145.202
    Amsterdam1, Netherlands: Packets lost (100%) 69.73.145.202
    Buenos Aires, Argentina: Packets lost (100%) 69.73.145.202
    Istanbul, Turkey: Packets lost (100%) 69.73.145.202
    Gdansk, Poland: Packets lost (100%) 69.73.145.202
    Beijing, China: Packets lost (100%) 69.73.145.202
    Belgrade, Serbia: Packets lost (100%) 69.73.145.202
    Toronto, Canada: Packets lost (100%) 69.73.145.202
    Novosibirsk, Russia: Packets lost (100%) 69.73.145.202
    Athens, Greece: Packets lost (100%) 69.73.145.202
    Frankfurt, Germany: Packets lost (100%) 69.73.145.202
    Sofia, Bulgaria: Packets lost (100%) 69.73.145.202
    Budapest, Hungary: Packets lost (100%) 69.73.145.202
    Sao Paulo, Brazil: Packets lost (100%) 69.73.145.202
      0 Not allowed!

  8. #48
    Join Date
    Oct 2009
    Posts
    36
    again, all servers down
      0 Not allowed!

  9. #49
    its down again !
      0 Not allowed!

  10. #50
    Join Date
    Jun 2011
    Posts
    76
    everything seems to be fine now
      0 Not allowed!

  11. #51
    Join Date
    Nov 2011
    Location
    Internet
    Posts
    114
    down again...
      0 Not allowed!

  12. #52
    mine down too!
      0 Not allowed!

  13. #53
    Join Date
    May 2005
    Location
    england
    Posts
    43
    Down again?
      0 Not allowed!

  14. #54
    Join Date
    Nov 2011
    Location
    Internet
    Posts
    114
    this is already very tired.
      0 Not allowed!

  15. #55
    Join Date
    May 2005
    Location
    england
    Posts
    43
    seems to be back again - both Jaguarpc and my server - been up and down all morning thus far, so fingers crossed
      0 Not allowed!

  16. #56
    There is a routing loop between some routers which belong to to the service providers through which the packets are routed to our servers. This is mainly related to not-fully propagated routes across the service provides around the world. Thus if a packet goes through the network which does not have updated records, it loops until the TTL of this packet is expired.

    We are working on this issue along with the DC techs and will try to get it resolved as quick as possible. The updates will follow on our forums.
    The network loop is noticed through nLayer, Tinet.net and perhaps others are involved. That means if packets from your end-devices are routed through these carriers, the packets will be looped until TTL of the packet is expired.

    We still work along with the DC techs to get this resolved but everything is fine inside our network. We just need the routes to get fully propagated to other service providers around the world.
      0 Not allowed!

  17. #57
    Join Date
    Nov 2011
    Location
    Internet
    Posts
    114
    I hope the problem is resolved quickly, this is tiring for our customers.
      0 Not allowed!

  18. #58
    Join Date
    Jul 2000
    Location
    Colorado Springs, CO
    Posts
    2,280
    We have added more links and capacity in recent weeks. I'm discussing this with our techs and engineers, there should be no lingering effects besides a faster network. This never should have happened, and nothing should still be happening. Definitely open tickets if you havent already.

    There was indeed some emergency network maintenance that took place this weekend that took down parts of the network. This is the first time in a long long many years we have had the network take down even our own site.

    We apologize for the inconvenience.
      0 Not allowed!

  19. #59
    Looks like the issues have appeared once again, some IP's are responding but the majority are down. The JaguarPC site is down once again so not possible to open any tickets, although on past form I doubt it would do any good
      0 Not allowed!

  20. #60

    JaguarPC unreachable again

    Hi,

    JaguarPC seem to have had another major outage right now, their website is unreachable, phones don't seem to get anywhere from UK. Any idea what's wrong? A power outage? Network outage? Any tips would be appreciated.

    Regards,
    Abbas
      0 Not allowed!

  21. #61
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    4,653
    All fine from here, UK also.
      0 Not allowed!

  22. #62
    Join Date
    Feb 2006
    Location
    Kepler 62f
    Posts
    14,662
    It's a network outage -- it started on 3/31, and has been repeating itself intermittently since.
    I think it's at their upstream/DC, not in the Jag network itself.

    .
    .
      0 Not allowed!

  23. #63
    Join Date
    Jun 2011
    Location
    Internet
    Posts
    2,573
    Fine from the UK and DE.
      0 Not allowed!

  24. #64
    Join Date
    Feb 2006
    Location
    Kepler 62f
    Posts
    14,662
    Quote Originally Posted by Flapadar View Post
    Fine from the UK and DE.
    From what Jag said yesterday, it's only affecting traffic that goes out on certain carriers. I would get alerts on one of my monitoring servers in NA, but not in Europe -- and vice versa.

    Yeah, it's annoying, but I have faith JPC is working on it. Or rather, working with their upstreams to get it fixed.

    When you pick a good host, you can rely on them to fix issues.

    .
    .
      0 Not allowed!

  25. #65
    Join Date
    Nov 2011
    Location
    Internet
    Posts
    114
    They said in their forum that the problem had been solved, we see that is not yet fully resolved.
      0 Not allowed!

  26. #66
    Join Date
    Jul 2006
    Location
    Australia
    Posts
    2,941
    Quote Originally Posted by Hexpress View Post
    They said in their forum that the problem had been solved, we see that is not yet fully resolved.
    That is what I got told when I reported the last outage.

    Just had another reply telling me what we all noticed didn't happen :/
      0 Not allowed!

  27. #67
    There was maintenance performed by Cogent. Thus we had to close the layer 2 link to Cogent. They anticipated the completion of the maintenance by 7:00 EST.

    Cogent's maint completed, the circuit was restored, the circuit was activated and all is functioning normally.
      0 Not allowed!

  28. #68
    There was maintenance performed by Cogent. Thus we had to close the layer 2 link to Cogent. They anticipated the completion of the maintenance by 7:00 EST.

    Cogent's maint completed, the circuit was restored, the circuit was activated and all is functioning normally.
      0 Not allowed!

  29. #69
    Join Date
    Oct 2007
    Location
    Vancouver/Hong Kong
    Posts
    1,248
    Looks like it is down again, and I just checked www.jaguarpc.com through just-ping.com and most locations show "unknown host"...
      0 Not allowed!

  30. #70
    Join Date
    Oct 2009
    Posts
    36
    again, jaguarpc is offline

    tested with just-ping.com

    Location Result min. rrt avg. rrt max. rrt IP
    Singapore, Singapore: Packets lost (80%) 281.3 281.6 281.9 69.73.138.32
    Amsterdam2, Netherlands: Unknown host: jaguarpc.com
    Florida, U.S.A.: Packets lost (100%) 69.73.138.32
    Amsterdam3, Netherlands: Packets lost (90%) 131.7 131.7 131.7 69.73.138.32
    Hong Kong, China: Unknown host: jaguarpc.com
    Sydney, Australia: Packets lost (90%) 248.1 248.1 248.1 69.73.138.32
    München, Germany: Unknown host: jaguarpc.com
    Cologne, Germany: Packets lost (100%) 69.73.138.32
    New York, U.S.A.: Packets lost (70%) 58.8 59.2 59.7 69.73.138.32
    Stockholm, Sweden: Packets lost (70%) 168.9 169.1 169.7 69.73.138.32
    Santa Clara, U.S.A.: Packets lost (70%) 94.6 95.4 96.2 69.73.138.32
    Vancouver, Canada: Packets lost (100%) 69.73.138.32
    London, United Kingdom: Packets lost (90%) 137.0 137.0 137.0 69.73.138.32
    Madrid, Spain: Unknown host: jaguarpc.com
    Padova, Italy: Unknown host: jaguarpc.com
    Austin, U.S.A.: Packets lost (90%) 70.9 70.9 70.9 69.73.138.32
    Amsterdam, Netherlands: Packets lost (70%) 139.5 140.1 141.1 69.73.138.32
    Paris, France: Packets lost (90%) 141.6 141.6 141.6 69.73.138.32
    Shanghai, China: Unknown host: jaguarpc.com
    Melbourne, Australia: Packets lost (100%) 69.73.138.32
    Copenhagen, Denmark: Unknown host: jaguarpc.com
    Lille, France: Packets lost (80%) 135.5 136.5 137.5 69.73.138.32
    San Francisco, U.S.A.: Unknown host: jaguarpc.com
    Zurich, Switzerland: Packets lost (100%) 69.73.138.32
    Mumbai, India: Packets lost (90%) 252.8 252.8 252.8 69.73.138.32
    Chicago, U.S.A.: Packets lost (90%) 50.8 50.8 50.8 69.73.138.32
    Nagano, Japan: Unknown host: jaguarpc.com
    Haifa, Israel: Packets lost (70%) 208.0 208.1 208.3 69.73.138.32
    Auckland, New Zealand: Unknown host: jaguarpc.com
    Antwerp, Belgium: Unknown host: jaguarpc.com
    Groningen, Netherlands: Packets lost (90%) 142.3 142.3 142.3 69.73.138.32
    Moscow, Russia: Unknown host: jaguarpc.com
    Dublin, Ireland: Packets lost (90%) 147.0 147.0 147.0 69.73.138.32
    Oslo, Norway: Packets lost (80%) 163.0 163.1 163.1 69.73.138.32
    Kharkov, Ukraine: Packets lost (90%) 188.0 188.0 188.0 69.73.138.32
    Manchester, United Kingdom: Unknown host: jaguarpc.com
    Vilnius, Lithuania: Packets lost (80%) 175.6 176.0 176.5 69.73.138.32
    Bucharest, Romania: Unknown host: jaguarpc.com
    Bangkok, Thailand: Packets lost (70%) 306.5 306.9 307.2 69.73.138.32
    Kuala Lumpur, Malaysia: Unknown host: jaguarpc.com
    Cape Town, South Africa: Unknown host: jaguarpc.com
    Glasgow, United Kingdom: Packets lost (80%) 126.5 126.9 127.2 69.73.138.32
    Lisbon, Portugal: Unknown host: jaguarpc.com
    Chicago, U.S.A.: Unknown host: jaguarpc.com
    Dallas, U.S.A.: Packets lost (80%) 58.0 59.0 60.1 69.73.138.32
    Cairo, Egypt: Unknown host: jaguarpc.com
    Amsterdam1, Netherlands: Unknown host: jaguarpc.com
    Buenos Aires, Argentina: Unknown host: jaguarpc.com
    Istanbul, Turkey: Unknown host: jaguarpc.com
    Gdansk, Poland: Unknown host: jaguarpc.com
    Beijing, China: Packets lost (100%) 69.73.138.32
    Belgrade, Serbia: Unknown host: jaguarpc.com
    Toronto, Canada: Unknown host: jaguarpc.com
    Novosibirsk, Russia: Packets lost (80%) 235.6 236.0 236.5 69.73.138.32
    Athens, Greece: Unknown host: jaguarpc.com
    Frankfurt, Germany: Packets lost (90%) 146.0 146.0 146.0 69.73.138.32
    Sofia, Bulgaria: Unknown host: jaguarpc.com
    Budapest, Hungary: Unknown host: jaguarpc.com
    Sao Paulo, Brazil: Packets lost (90%) 210.8 210.8 210.8 69.73.138.32
      0 Not allowed!

  31. #71
    It's working for me although the VPS seems slowed
      0 Not allowed!

  32. #72
    Join Date
    Oct 2009
    Posts
    36
    Quote Originally Posted by stoppingfear View Post
    It's working for me although the VPS seems slowed
    network back up 3 minutes ago
      0 Not allowed!

  33. #73
    Join Date
    Oct 2007
    Location
    Vancouver/Hong Kong
    Posts
    1,248
    Back online now
      0 Not allowed!

  34. #74
    Join Date
    Jan 2011
    Posts
    98
    back online but has intermittent down time..
    Hope JaguarPC give compensation for this.
      0 Not allowed!

  35. #75
    Join Date
    May 2009
    Location
    Hong Kong
    Posts
    207
    My server is ok
      0 Not allowed!

  36. #76
    Join Date
    Apr 2011
    Posts
    53
    One of my vps(LA) with them was down, send a ticket, 1 hours now, still no reply
      0 Not allowed!

  37. #77
    Quote Originally Posted by kumpachi View Post
    back online but has intermittent down time..
    Hope JaguarPC give compensation for this.
    http://www.webhostingtalk.com/showpo...&postcount=126

    Not too sure if this is legitimate but it seems like a fair compensation.

    I wasn't going to claim it but I think with all the downtime throughout this month (3-4 times?) I might give it a try.
      0 Not allowed!

  38. #78
    Join Date
    Jul 2006
    Location
    Australia
    Posts
    2,941
    Quote Originally Posted by stoppingfear View Post
    http://www.webhostingtalk.com/showpo...&postcount=126

    Not too sure if this is legitimate but it seems like a fair compensation.

    I wasn't going to claim it but I think with all the downtime throughout this month (3-4 times?) I might give it a try.
    That was for their VPS downtime though and not the network time.
      0 Not allowed!

  39. #79

    Hello

    That compensation was for downtime on one of our UK servers. If you still are having troubles with your VPS, please open a support ticket.

    <<signatures to be set up in your profile>>
    Last edited by bear; 04-10-2012 at 08:57 AM.
      0 Not allowed!

  40. #80
    Quote Originally Posted by BeZazz View Post
    That was for their VPS downtime though and not the network time.
    Ah yeh, Just searched up their SLA:
    If network downtime occurs the customer will be credited 10x (1000%) of the downtime as recorded by the support ticket and confirmed problem to the resolution, up to 100% of the customer's monthly fee. If the network is out for 1 hour, we will credit you 10 hours of downtime. In this instance we divide your monthly payment by days of the month, divided by 24hrs a day to find an hour rate. That amount will be credited to your account towards your next invoice.
    I guess that's the compensation; from the ticket response I got:
    After the end of the month we can evaluate the total downtime and issue a credit as per the SLA. Thanks for your patience and please let us know if we can be of further assistance.


    Quote Originally Posted by MrShades View Post
    That compensation was for downtime on one of our UK servers. If you still are having troubles with your VPS, please open a support ticket.

    Matt | CSR
    Jaguarpc.com
    So Let me know if I got this right:

    Assuming a $72 VPS
    72/720= 0.125

    0.125*10=1.25

    1.25*1 hour downtime = $1.25
    1.25*2 hour downtime = $2.50
    1.25*3 Hour downtime = $3.75
    1.25*4 Hour Downtime = $5.00
    Last edited by stoppingfear; 04-09-2012 at 04:04 PM.
      0 Not allowed!

Page 2 of 2 FirstFirst 12

Similar Threads

  1. vbulletin.com's new site and vB 4.0[merged]
    By RS Shamil in forum Web Hosting Lounge
    Replies: 460
    Last Post: 01-05-2010, 05:43 AM
  2. How much is your site worth? [merged]
    By Webdude in forum Web Hosting Lounge
    Replies: 40
    Last Post: 05-19-2007, 08:24 PM
  3. HSphere Site [merged]
    By networkegypt in forum Providers and Network Outages and Updates
    Replies: 26
    Last Post: 03-11-2007, 03:17 PM
  4. IS Jaguar PC under Attack? Seems like their Site is slow,
    By Energizer Bunny in forum VPS Hosting
    Replies: 2
    Last Post: 07-30-2006, 10:38 PM
  5. hosting my site [merged]
    By cardwell in forum Web Hosting
    Replies: 22
    Last Post: 03-18-2005, 11:25 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •