Skip to main content

AS213880

JORGE-JANAITE-NETO

------------------------------------------------------------

Registry

Authoritative registration data

AS number
213880
Name
JORGE-JANAITE-NETO
Organisation
------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS213880
2a01:e281:b200::/48 IPv6 /48 not checked
2a01:e281:b201::/48 IPv6 /48 not checked
2a01:e281:b202::/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

Internet Exchange memberships listed for AS213880
Address families
FREMIX 1,000 Mbps IPv6
FogIXP 1,000 Mbps IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv6
ONIX 1,000 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 AS213880 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS213880 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 231 620
v6
AS21738 ROZINT 191 269
v6
AS52025 PARADOXNETWORKS-LIMITED 75 123
v6
AS34872 Servperso_Systems 39 53
v6
AS25091 IP-Max 3 5
v6
AS8298 IPNG 2 2
v6
AS34927 iFog-GmbH 2 2
v6
AS20473 AS-VULTR 1 2
v6
AS205794 RTTW-AS 1 1
v6
AS401753 BIXCE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS213880 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS199854 ITBYPASSION 1 1
v6
AS403001 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.