If anyone cannot go to 2checkout site,please send email to inform them.
Yesterday,I could not go to their site but I could send email to them.
Let them know so many people cannot login to the reseller a/c.
Last edited by zhaozilong; 08-31-2002 at 07:36 PM.
Not down, but some of our past sales' IP addresses were incorrectly located:
High Risk Order Warning!!
The buyer appears to be in United Kingdom but the billing country is Canada.
Buyer location (Certainty - 74%): London,England United Kingdom
2Checkout.com recommends that you scrutinize this order very closely for possible fraud. Each merchant should make their own determination as to whether the order should be fulfilled. It is further recommended that this order not be fulfilled for 24 hours, to ensure that it was reviewed by the 2Checkout.com fraud department.
Funny part is one of these was done right from my home PC (wanted to test this). Apparently Canada's been conquered by the Brits and as always I'm the last to know.
Are 2checkout located in the ventures online data centre? I can't get to anyone located in ventures online (been like this for around 36 hours). The problem is for AU customers who are going through Telstra. Telstra suck so hard!
Tracing route to 2checkout.com [220.127.116.11]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
<< removed >>
4 23 ms 25 ms 26 ms atm2-0-33.cor1.syd2.internode.on.net [150.101.22
5 26 ms 24 ms 24 ms ATM5-1-0--7.ken11.Sydney.telstra.net [139.130.18
6 30 ms 26 ms 27 ms GigabitEthernet0-0.ken-core4.Sydney.telstra.net
7 25 ms 23 ms 32 ms Pos2-0.pad-core4.Sydney.telstra.net [18.104.22.168
8 26 ms 24 ms 26 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
9 211 ms 214 ms 212 ms 22.214.171.124
10 278 ms 278 ms 278 ms 126.96.36.199
11 311 ms 310 ms 311 ms 188.8.131.52
12 316 ms 311 ms 317 ms 184.108.40.206
13 311 ms 312 ms 312 ms 220.127.116.11
14 286 ms 287 ms 288 ms p3-1.nycmny1-cr2.bbnplanet.net [18.104.22.168]
15 289 ms 285 ms 290 ms p0-0.nycmny1-nbr2.bbnplanet.net [22.214.171.124]
16 289 ms 287 ms 286 ms p15-0.nycmny1-nbr1.bbnplanet.net [126.96.36.199]
17 288 ms 295 ms 289 ms so-6-0-0.chcgil2-br2.bbnplanet.net [188.8.131.52]
18 285 ms 286 ms 315 ms so-1-0-0.dnvtco1-br2.bbnplanet.net [184.108.40.206]
19 291 ms 292 ms 291 ms so-7-0-0.dnvtco1-br1.bbnplanet.net [220.127.116.11]
20 284 ms 288 ms 286 ms p1-0.dnvtco1-cr1.bbnplanet.net [18.104.22.168]
21 285 ms 295 ms 287 ms gigabitethernet0.yipes9.bbnplanet.net [22.214.171.124
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.
Yep that's the same tracert I've bee getting trying to reach www.sitepointfourms.com over the last day and a bit. It dies after
I put a request in with my ISP, internode, to reroute this traffic through their UUNET connection - waiting.
Seems they know about the problem here is their reply to me.:>
The message we received from our Network Service Provider is as follows:
There is a routing issue on the Internet due to Reach Networks peering. This is affecting some of our overseas customers. We have tried to route around it on our end, but are unable to influence the path away from this route point. Reach continues to advertise routes but are not able to forward the traffic, thus blackholing some of the Internet. We are trying to contact someone to fix it at their end, but are not able to reach anyone. We are also working with our carriers to de-peer them or stop those routes from being announced, but we feel that this may not resolve the issue unless Reach can fix the problem on their end. The carriers are trying to reach Reach Networks also.
This issue is out of our reach, but we are confident that our provider will pursue this issue.
I love the part of how it out of their Reach but the part I love most is the this.