https://www.nedbank.co.za/ unreachable on telkom Mobile [SOLVED]

dotcat

Expert Member
Joined
Nov 18, 2005
Messages
1,076
Can anyone else reach https://www.nedbank.co.za/

ing has started…

PING www.nedbank.co.za (168.142.204.15): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- www.nedbank.co.za ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
 

supersunbird

Honorary Master
Joined
Oct 1, 2005
Messages
60,141
I can reach them fine on my capped Telkom Mobile account.

Can't ping them though.
 

Nerfherder

Honorary Master
Joined
Apr 21, 2008
Messages
29,703
Can anyone else reach https://www.nedbank.co.za/

ing has started…

PING www.nedbank.co.za (168.142.204.15): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- www.nedbank.co.za ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

Do a trace route as they probably ignore ping requests.


Tracert www.nedbank.co.za
 

dotcat

Expert Member
Joined
Nov 18, 2005
Messages
1,076
Traceroute has started…

traceroute to netbank.nedsecure.co.za (168.142.204.33), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3.206 ms 1.195 ms 1.350 ms
2 192.168.2.1 (192.168.2.1) 6.915 ms 2.832 ms 1.611 ms
3 * * *
4 105-187-252-221.ti-sen.telkomsa.net (105.187.252.221) 23.663 ms 20.494 ms 21.031 ms
5 cust-aggr-1.east.telkomsa.net (105.229.0.29) 20.377 ms 26.335 ms 20.277 ms
6 105-187-252-102.ti-sen.telkomsa.net (105.187.252.102) 35.874 ms 31.126 ms 30.679 ms
7 105-187-252-102.ti-sen.telkomsa.net (105.187.252.102) 31.173 ms 33.421 ms 33.257 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
 

dotcat

Expert Member
Joined
Nov 18, 2005
Messages
1,076
ok it was the webdeveloper chrome extension that has been hacked - remove it at once!
 
Top