Skip to main content

AS207234

AS-MBN

Cogent

Registry

Authoritative registration data

AS number
207234
Name
AS-MBN
Organisation
Cogent
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS207234
185.60.196.0/22 IPv4 /22 not checked
194.39.178.0/23 IPv4 /23 not checked
194.39.212.0/23 IPv4 /23 not checked
185.60.196.0/24 IPv4 /24 RPKI valid
185.60.197.0/24 IPv4 /24 RPKI valid
185.60.198.0/24 IPv4 /24 RPKI valid
185.60.199.0/24 IPv4 /24 RPKI valid
194.39.178.0/24 IPv4 /24 RPKI valid
194.39.179.0/24 IPv4 /24 RPKI valid
194.39.212.0/24 IPv4 /24 not checked
194.39.213.0/24 IPv4 /24 RPKI valid
2a02:7520::/32 IPv6 /32 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

49 networks seen before AS207234 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207234 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

47 adjacencies that may be an artefact of collector peering

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.