Skip to main content

AS62310

MH-DC-AS

---------------------------------------------

Registry

Authoritative registration data

AS number
62310
Name
MH-DC-AS
Organisation
---------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS62310
77.220.248.0/21 IPv4 /21 not checked
2a02:2878:8000::/34 IPv6 /34 RPKI valid

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 AS62310
Address families
BCIX: BCIX Peering LAN 10,000 Mbps IPv4 · IPv6

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 AS62310 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS62310 in AS paths

Observed upstreams
Families
AS5405 INTERDOTLINK 206 454
v4 v6
AS3356 LEVEL3 63 110
v4 v6
AS6939 HURRICANE 66 90
v4 v6
AS8218 NEO-ASN 4 21
v4 v6
AS9002 RETN-AS 6 10
v6
AS24961 MYLOC-AS 2 4
v4 v6
AS6797 GLOBALCONNECT-NET 1 4
v4 v6
AS39351 ESAB-AS 2 3
v4 v6
AS33891 CORE-BACKBONE 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS62310 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
AS24482 SGGS-AS-AP 1 8
v4 v6
AS680 DFN 1 2
v4 v6
AS50629 LWLCOM 1 2
v4 v6
AS13237 LAMBDANET-AS 1 1
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.