Skip to main content

AS213015

RB67NET

RB67 Networks

Registry

Authoritative registration data

AS number
213015
Name
RB67NET
Organisation
RB67 Networks
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

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

Prefixes announced by AS213015
2a0c:b641:5b4::/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 AS213015
Address families
EVIX: Peering LAN 2,000 Mbps IPv6
FogIXP 1,000 Mbps IPv6
FogIXP Frankfurt 1,000 Mbps 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 AS213015 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS213015 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 164 241
v6
AS34927 iFog-GmbH 74 95
v6
AS25091 IP-Max 3 5
v6
AS39351 ESAB-AS 2 2
v6
AS211509 2 2
v6
AS50869 FREEIX-REMOTE 1 1
v6
AS205794 RTTW-AS 1 1
v6
AS209022 Tschajera-Limited 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS213015 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v6
AS51184 1 2
v6
AS8298 IPNG 1 1
v6
AS25220 GLOBALNOC-AS 1 1
v6
AS41666 1 1
v6
AS50629 LWLCOM 1 1
v6
AS57821 1 1
v6
AS58057 SECUREBIT 1 1
v6
AS58299 OPENFACTORY-AS 1 1
v6
AS209823 1 1
v6
AS215628 AS-XENOX-AT 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.