Skip to main content

AS212123

REDPANDA-AS

Red Panda Network

Registry

Authoritative registration data

AS number
212123
Name
REDPANDA-AS
Organisation
Red Panda Network
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

5

Total announced

9

Announced prefixes

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

Prefixes announced by AS212123
167.150.90.0/23 IPv4 /23 not checked
185.133.211.0/24 IPv4 /24 RPKI valid
212.94.55.0/24 IPv4 /24 not checked
45.129.94.0/24 IPv4 /24 not checked
2001:678:110::/48 IPv6 /48 not checked
2001:67c:e70::/48 IPv6 /48 not checked
2001:67c:e74::/48 IPv6 /48 not checked
2001:67c:e78::/48 IPv6 /48 not checked
2602:fe2e:fff::/48 IPv6 /48 RPKI valid

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 AS212123
Address families
LOCIX FRANKFURT: Peering LAN 10,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 AS212123 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS212123 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 172 949
v4 v6
AS34549 MEER-AS 119 460
v4 v6
AS21700 NEPTUNE-NETWORKS 216 292
v6
AS200462 AS-ETH 63 273
v4 v6
AS34854 BLAHAJ-CLOUD 47 223
v4 v6
AS25091 IP-Max 5 44
v4 v6
AS37989 DCS1PTELTD-AS-AP 6 28
v4 v6
AS14840 ASN14840 2 15
v4
AS8298 IPNG 2 11
v4 v6
AS211509 RUDAKI-AS 4 10
v6
AS58299 OPENFACTORY-AS 3 9
v4 v6
AS401753 BIXCE 1 8
v4 v6
AS31500 GNM-AS 1 4
v4
AS48646 STEFAN6 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS212123 in AS paths

Observed downstreams
Families
AS207424 HYNET 16 19
v6

No rows match “”.

Showing – of

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

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.