Skip to main content

AS214309

AURORIX

ORG-AGSL6-RIPE

Registry

Authoritative registration data

AS number
214309
Name
AURORIX
Organisation
ORG-AGSL6-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

4

Total announced

6

Announced prefixes

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

Prefixes announced by AS214309
185.176.94.0/24 IPv4 /24 not checked
89.35.130.0/24 IPv4 /24 not checked
2a12:bec4:14d0::/44 IPv6 /44 not checked
2a12:bec4:1f50::/44 IPv6 /44 not checked
2a0d:d940:2015::/48 IPv6 /48 not checked
2a0d:d940:9015::/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 AS214309 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS214309 in AS paths

Observed upstreams
Families
AS62255 BEMYLINK 789 1,407
v4 v6
AS199524 GCORE 255 662
v4
AS35598 32 50
v4 v6
AS216039 4 5
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS214309 in AS paths

Observed downstreams
Families
AS202610 251 343
v6
AS216039 252 341
v6
AS219319 64 87
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
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.