Skip to main content

AS57025

MoNetworks

MonoCloud Pty Ltd

Registry

Authoritative registration data

AS number
57025
Name
MoNetworks
Organisation
MonoCloud Pty Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS57025
103.181.1.0/24 IPv4 /24 not checked
160.250.13.0/24 IPv4 /24 not checked
45.8.204.0/24 IPv4 /24 not checked
2a13:db01:1000::/36 IPv6 /36 not checked
2400:56a0:200::/40 IPv6 /40 RPKI valid
2400:56a0:900::/40 IPv6 /40 not checked
2400:56a0:dc02::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS57025 in AS paths

Observed upstreams
Families
AS60068 CDN77 468 1,062
v4 v6
AS3491 PCCWG-APAC-HK 222 743
v4 v6
AS6939 HURRICANE 107 401
v4 v6
AS24482 SGGS-AS-AP 2 56
v4 v6
AS20485 TRANSTELECOM 4 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS57025 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
AS35280 F5 1 5
v4 v6
AS49544 i3Dnet 1 5
v4 v6
AS59105 HOMENOC 1 5
v4 v6
AS17639 CONVERGE-AS 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.