bgpreport

Network · data from 2026-11-12

AS20811 Brennercom

Registry name: BRENNERCOM-AS Retelit Digital Services S.p.A., IT · PeeringDB

14IPv4 routes 100.0% RPKI valid · 92.9% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS20811, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20811, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
84.18.147.0/24 Valid Nonecovered by 84.18.128.0/19 671 100% 67
37.186.128.0/18 Valid RIR databaseRIPE 672 100% 67
46.234.224.0/19 Valid RIR databaseRIPE 672 100% 67
77.74.112.0/21 Valid RIR databaseRIPE 672 100% 67
84.18.128.0/19 Valid RIR databaseRIPE 672 100% 67
89.190.160.0/19 Valid RIR databaseRIPE 672 100% 67
93.89.48.0/20 Valid RIR databaseRIPE 672 100% 67
95.171.32.0/19 Valid RIR databaseRIPE 672 100% 67
109.69.248.0/21 Valid RIR databaseRIPE 672 100% 67
217.199.0.0/19 Valid RIR databaseRIPE 672 100% 67
147.189.208.0/24 Valid RIR databaseRIPE 670 100% 67
147.189.209.0/24 Valid RIR databaseRIPE 670 100% 67
185.6.192.0/22 Valid RIR databaseRIPE 670 100% 67
185.111.144.0/22 Valid RIR databaseRIPE 670 100% 67
2a02:490::/29 Valid RIR databaseRIPE 633 100% 67
2a02:54c0::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS20811: AS-BCOMIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS20811 isn't in the set, or no route object for AS20811 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS20811 in itNot covered
AS-BCOMIT RIPE 274328 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none84.18.147.0/24No route object for it. A route object for 84.18.128.0/19 with origin AS20811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20811 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS20811 whose prefix no peer sees AS20811 announce. Many are kept on purpose (backup routes, space announced only in some places).

94.126.188.0/23RIPENo ROA
109.69.252.0/22RIPEValid
212.46.160.0/21RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.