Skip to main content

AS29413

KOMRO-AS

Komro Telekommunikations GmbH

Registry

Authoritative registration data

AS number
29413
Name
KOMRO-AS
Organisation
Komro Telekommunikations GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

2

Total announced

16

Announced prefixes

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

Prefixes announced by AS29413
213.149.80.0/20 IPv4 /20 not checked
213.178.16.0/20 IPv4 /20 not checked
217.72.208.0/20 IPv4 /20 not checked
37.156.80.0/20 IPv4 /20 not checked
88.133.160.0/20 IPv4 /20 not checked
46.31.216.0/21 IPv4 /21 not checked
88.133.224.0/21 IPv4 /21 not checked
185.214.120.0/22 IPv4 /22 not checked
185.31.60.0/22 IPv4 /22 not checked
185.91.48.0/22 IPv4 /22 not checked
31.187.80.0/22 IPv4 /22 not checked
31.187.88.0/22 IPv4 /22 not checked
31.187.88.0/24 IPv4 /24 not checked
91.217.176.0/24 IPv4 /24 not checked
2a02:2488::/32 IPv6 /32 RPKI valid
2a0b:9940::/32 IPv6 /32 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 AS29413
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 50,000 Mbps IPv4 · IPv6
DE-CIX Munich: DE-CIX Munich Peering LAN 50,000 Mbps IPv4 · IPv6
SAIX: Public Peering LAN 5,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 AS29413 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

29 networks seen before AS29413 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS29413 in AS paths

Observed downstreams
Families
AS49696 ROCT 322 495
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

62 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 105
v4 v6
AS12779 ITGATE 2 68
v4 v6
AS47147 AS-ANX 2 59
v4 v6
AS24482 SGGS-AS-AP 2 49
v4 v6
AS25091 IP-Max 2 49
v4 v6
AS49544 i3Dnet 2 32
v4 v6
AS15547 NETPLUS 2 31
v4 v6
AS8529 OMANTEL-AS 1 30
v4 v6
AS35710 WEBERCLOUD 1 30
v4 v6
AS47692 NESSUS 1 30
v4 v6
AS51184 FONIRA 1 30
v4 v6
AS212483 level86 2 28
v4
AS553 BELWUE 2 17
v4 v6
AS680 DFN 2 17
v4 v6
AS3212 TELEMACH 2 17
v4 v6
AS8298 IPNG 2 17
v4 v6
AS8888 XTOM 2 17
v4 v6
AS20932 SIG-ST 2 17
v4 v6
AS25220 GLOBALNOC-AS 2 17
v4 v6
AS29140 HOSTSERVER-AS 2 17
v4 v6
AS29691 NINE 2 17
v4 v6
AS35360 GARGUNET 2 17
v4 v6
AS35369 LINZAG-TELEKOM-AS 2 17
v4 v6
AS41327 FIBERTELECOM-AS 2 17
v4 v6
AS42541 FIBERBY 2 17
v4 v6
AS48919 UA-CITY-AS 2 17
v4 v6
AS58057 SECUREBIT 2 17
v4 v6
AS58299 OPENFACTORY-AS 2 17
v4 v6
AS61573 ASN61573 2 17
v4 v6
AS199938 NETZWERGE 2 17
v4 v6
AS209823 ENKI-AS 2 17
v4 v6
AS213151 CHRISELSEN 2 17
v4 v6
AS264479 ASN264479 2 17
v4 v6
AS559 Switch 2 16
v4 v6
AS25160 VORBOSS 2 16
v4 v6
AS31510 IKB-AS 2 16
v4 v6
AS36236 NETACTUATE 2 16
v4 v6
AS45489 SLT-GLOBAL 2 16
v4 v6
AS56987 AS-ABACLOUDA 2 16
v4 v6
AS3214 XTOM 1 15
v4 v6
AS29075 IELO 1 15
v4 v6
AS35280 F5 1 15
v4 v6
AS64475 FREIFUNK-FRANKFURT 1 15
v4 v6
AS199524 GCORE 1 15
v4 v6
AS13237 LAMBDANET-AS 2 14
v4
AS14630 INVESCO 2 14
v4
AS21412 CGATES-AS 2 14
v4
AS142271 DOUBLESQUARE-AS-AP 2 14
v4
AS198150 SIACOM-AS 2 14
v4
AS206356 Freifunk-Essen 2 14
v4
AS210937 Showfom 2 14
v4
AS35598 INETCOM 1 13
v4
AS37721 ORG-VTS1-AFRINIC 1 13
v4
AS205112 PHILUNET 1 13
v4
AS57777 MASSAR 2 4
v4 v6
AS28917 Fiord-AS 1 4
v6
AS1828 UNITAS 2 3
v6
AS51185 MAINSTREAMING-AS 2 3
v6
AS198249 OPSONE 2 3
v6
AS213241 TECHIT 2 3
v6
AS17639 CONVERGE-AS 1 2
v4 v6
AS49696 ROCT 1 2
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.