Skip to main content

AS200712

OUTPOST24

-----

Registry

Authoritative registration data

AS number
200712
Name
OUTPOST24
Organisation
-----
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 AS200712
185.92.170.0/24 IPv4 /24 RPKI valid
80.254.231.0/24 IPv4 /24 not checked
91.216.32.0/24 IPv4 /24 RPKI valid
2a13:5240::/32 IPv6 /32 RPKI valid
2a13:5242::/32 IPv6 /32 RPKI valid
2a13:5245::/32 IPv6 /32 RPKI valid
2001:67c:1084::/48 IPv6 /48 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 AS200712
Address families
SONIX Stockholm 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 AS200712 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS200712 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 197 1,269
v4 v6
AS1257 SWIPNET 65 551
v4 v6
AS6939 HURRICANE 88 486
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200712 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS6667 EUNET-FINLAND 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.