Skip to main content

AS211251

A1-DC

A1 Internet BV

Registry

Authoritative registration data

AS number
211251
Name
A1-DC
Organisation
A1 Internet BV
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

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

Prefixes announced by AS211251
213.171.64.0/23 IPv4 /23 not checked
213.171.66.0/23 IPv4 /23 not checked
213.171.68.0/23 IPv4 /23 not checked
213.171.67.0/24 IPv4 /24 not checked
213.171.72.0/24 IPv4 /24 not checked
213.171.73.0/24 IPv4 /24 not checked
213.171.74.0/24 IPv4 /24 not checked
213.171.75.0/24 IPv4 /24 not checked
79.98.176.0/24 IPv4 /24 not checked
79.98.177.0/24 IPv4 /24 not checked
79.98.179.0/24 IPv4 /24 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 AS211251 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS211251 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS211251 in AS paths

Observed downstreams
Families
AS203966 a1-as 140 158
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 18
v4
AS3399 OBE-NET 2 9
v4
AS34019 HIVANE 2 9
v4
AS34927 iFog-GmbH 2 9
v4
AS37721 ORG-VTS1-AFRINIC 2 9
v4
AS49544 i3Dnet 2 9
v4
AS263152 ASN263152 2 9
v4
AS25091 IP-Max 1 1
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.