Skip to main content

AS207466

SBFR

Registry

Authoritative registration data

AS number
207466
Name
SBFR
Organisation
SBFR
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

4

Total announced

4

Announced prefixes

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

Prefixes announced by AS207466
2a0a:6040:d900::/40 IPv6 /40 RPKI valid
2a06:a001:a080::/44 IPv6 /44 RPKI valid
2a06:a005:15d2::/48 IPv6 /48 RPKI valid
2a06:a005:15d3::/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 AS207466
Address families
1-NL FREE 10,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps 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 AS207466 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS207466 in AS paths

Observed upstreams
Families
AS53667 PONYNET 225 609
v6
AS198831 HOLYCLOUD 237 437
v6
AS20473 AS-VULTR 61 76
v6
AS6939 HURRICANE 21 25
v6
AS44103 BAKKER-IT-AS 16 19
v6
AS202580 AS-1-NL 6 7
v6
AS212895 ROUTE64_ORG 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207466 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
AS209823 ENKI-AS 1 1
v6

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.