Skip to main content

AS213027

INFRARUN

infra.run Service GmbH

Registry

Authoritative registration data

AS number
213027
Name
INFRARUN
Organisation
infra.run Service GmbH
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

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

Prefixes announced by AS213027
45.92.48.0/22 IPv4 /22 not checked
45.92.48.0/24 IPv4 /24 not checked
45.92.49.0/24 IPv4 /24 not checked
45.92.50.0/24 IPv4 /24 not checked
45.92.51.0/24 IPv4 /24 not checked
91.203.106.0/24 IPv4 /24 not checked
2a11:a00::/29 IPv6 /29 not checked
2001:678:f70::/48 IPv6 /48 not checked
2001:678:f74::/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 AS213027
Address families
BCIX: BCIX 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 AS213027 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS213027 in AS paths

Observed upstreams
Families
AS9136 269 2,414
v4 v6
AS6939 HURRICANE 78 385
v4 v6
AS8218 NEO-ASN 5 96
v4 v6
AS24482 SGGS-AS-AP 2 84
v4 v6
AS9002 RETN-AS 8 39
v6
AS24961 2 18
v4 v6
AS39351 ESAB-AS 2 18
v4 v6
AS6797 GLOBALCONNECT-NET 1 18
v4 v6
AS20562 OPEN-PEERING-AS 1 4
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS213027 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
AS680 1 9
v4 v6
AS13237 LAMBDANET-AS 1 6
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.