Skip to main content

AS65500

Private use AS

Registry

Authoritative registration data

AS number
65500
Name
Private use AS
Organisation
—
Country
—
RIR
—
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS65500
192.36.103.0/24 IPv4 /24 RPKI not found
194.14.237.0/24 IPv4 /24 RPKI not found
2403:2c00:f02f::/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 AS65500 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS65500 in AS paths

Observed upstreams
Families
AS577 BACOM 2 10
v4
AS65522 2 10
v6
AS8473 BAHNHOF 3 6
v4
AS56974 SRC_OF_RA-AS 4 4
v4
AS65087 2 3
v6
AS61893 ASN61893 1 1
v6
AS265340 ASN265340 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS65500 in AS paths

Observed downstreams
Families
AS54941 NETWORK-01 2 10
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS262206 262206 1 7
v4 v6
AS29680 VOZTELECOM 1 5
v4
AS57381 FNUTT 1 3
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.