Skip to main content

AS212660

WHG-DXB1

WHG Hosting Services Ltd

Registry

Authoritative registration data

AS number
212660
Name
WHG-DXB1
Organisation
WHG Hosting Services Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS212660
198.38.94.0/24 IPv4 /24 not checked
198.38.95.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS212660
Address families
SH-IX 10,000 Mbps IPv4
UAE-IX: UAE-IX Peering LAN 10,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS212660 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS212660 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 154 442
v4
AS3257 GTT-BACKBONE 111 292
v4
AS35280 F5 4 8
v4
AS286 KPN 1 2
v4
AS17557 PKTELECOM-AS-PK 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS212660 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8529 OMANTEL-AS 1 4
v4
AS36236 NETACTUATE 1 2
v4
AS49544 i3Dnet 1 2
v4
AS200612 GulfBridgeInternational 1 2
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.