Skip to main content

AS250

SACREDCHAO-AS

AS250.net Foundation

Registry

Authoritative registration data

AS number
250
Name
SACREDCHAO-AS
Organisation
AS250.net Foundation
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS250
193.227.234.0/23 IPv4 /23 not checked
194.150.168.0/23 IPv4 /23 not checked
195.245.114.0/23 IPv4 /23 not checked
195.85.254.0/24 IPv4 /24 not checked
2001:4ce8::/32 IPv6 /32 not checked

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 AS250
Address families
BCIX: BCIX Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Hamburg: DE-CIX Hamburg Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Munich: DE-CIX Munich Peering LAN 10,000 Mbps IPv4 · IPv6
FIXO 1,000 Mbps IPv4
NL-ix: Main 10,000 Mbps IPv4 · IPv6
SOLIX MTU1500 1,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 AS250 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS250 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS250 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

42 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.