Skip to main content

AS63129

AIRRABBIT-NETWORK

AirRabbit, LLC

Registry

Authoritative registration data

AS number
63129
Name
AIRRABBIT-NETWORK
Organisation
AirRabbit, LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

47

Total announced

56

Announced prefixes

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

Prefixes announced by AS63129
130.51.96.0/24 IPv4 /24 not checked
130.51.97.0/24 IPv4 /24 not checked
130.51.98.0/24 IPv4 /24 not checked
130.51.99.0/24 IPv4 /24 not checked
155.103.152.0/24 IPv4 /24 not checked
155.103.153.0/24 IPv4 /24 not checked
155.103.154.0/24 IPv4 /24 not checked
155.103.155.0/24 IPv4 /24 not checked
23.137.52.0/24 IPv4 /24 not checked
2602:f688:1000::/36 IPv6 /36 not checked
2602:f688:2000::/36 IPv6 /36 not checked
2602:f688:3000::/36 IPv6 /36 not checked
2602:f688:4000::/36 IPv6 /36 not checked
2602:f688:5000::/36 IPv6 /36 not checked
2602:f688:6000::/36 IPv6 /36 not checked
2602:f688:7000::/36 IPv6 /36 not checked
2602:f688:8000::/36 IPv6 /36 not checked
2602:f688:9000::/36 IPv6 /36 not checked
2602:f688::/36 IPv6 /36 not checked
2602:f688:a000::/36 IPv6 /36 not checked
2602:f688:b000::/36 IPv6 /36 not checked
2602:f688:c000::/36 IPv6 /36 not checked
2602:f688:d000::/36 IPv6 /36 not checked
2602:f688:e000::/36 IPv6 /36 not checked
2602:f7d5:1000::/36 IPv6 /36 not checked
2602:f7d5:2000::/36 IPv6 /36 not checked
2602:f7d5:3000::/36 IPv6 /36 not checked
2602:f7d5:4000::/36 IPv6 /36 not checked
2602:f7d5:5000::/36 IPv6 /36 not checked
2602:f7d5:6000::/36 IPv6 /36 not checked
2602:f7d5:7000::/36 IPv6 /36 not checked
2602:f7d5:8000::/36 IPv6 /36 not checked
2602:f7d5:9000::/36 IPv6 /36 not checked
2602:f7d5::/36 IPv6 /36 not checked
2602:f7d5:a000::/36 IPv6 /36 not checked
2602:f7d5:b000::/36 IPv6 /36 not checked
2602:f7d5:c000::/36 IPv6 /36 not checked
2602:f7d5:d000::/36 IPv6 /36 not checked
2602:f7d5:e000::/36 IPv6 /36 not checked
2602:f7d5:f000::/36 IPv6 /36 not checked
2602:f87f:1000::/36 IPv6 /36 not checked
2602:f87f:2000::/36 IPv6 /36 not checked
2602:f87f:3000::/36 IPv6 /36 not checked
2602:f87f:4000::/36 IPv6 /36 not checked
2602:f87f:5000::/36 IPv6 /36 not checked
2602:f87f:6000::/36 IPv6 /36 not checked
2602:f87f:7000::/36 IPv6 /36 not checked
2602:f87f:8000::/36 IPv6 /36 not checked
2602:f87f:9000::/36 IPv6 /36 not checked
2602:f87f::/36 IPv6 /36 not checked
2602:f87f:a000::/36 IPv6 /36 not checked
2602:f87f:b000::/36 IPv6 /36 not checked
2602:f87f:c000::/36 IPv6 /36 not checked
2602:f87f:d000::/36 IPv6 /36 not checked
2602:f87f:e000::/36 IPv6 /36 not checked
2602:f87f:f000::/36 IPv6 /36 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 AS63129
Address families
JEIX 10,000 Mbps IPv4 · IPv6
SFMIX 1,000 Mbps IPv4 · 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 AS63129 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS63129 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 321 19,735
v4 v6
AS400587 RYAMER 240 604
v4
AS10111 1 47
v6
AS6424 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS63129 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
AS49544 i3Dnet 1 112
v4 v6
AS36236 NETACTUATE 1 56
v4 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.