bgpreport

Network · data from 2026-11-12

AS266245 Burda Comercio e Serviços

Registry name: AS266245 - Burda Comercio e Servicos Ltda Me, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266245, 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.

45.6.200.0/22 No ROA Other IRR onlyALTDB, RADB, TC 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS266245: AS-CLICKNETTELECOM. 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 (AS266245 isn't in the set, or no route object for AS266245 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 objectsAS266245 in itNot covered
AS-CLICKNETTELECOM In no IRR database read today.

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 12 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • AS-SET: not found1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none45.6.200.0/22No ROA covers it. Add a ROA for AS266245, maxLength 22.671 of 673
Route object: RIR45.6.200.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
AS-SET: not foundAS-CLICKNETTELECOMPeeringDB names AS-CLICKNETTELECOM; no IRR database read has it.

Route objects not announced

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

45.6.200.0/23RADBNo ROA
45.6.200.0/24RADBNo ROA
45.6.201.0/24RADBNo ROA
45.6.202.0/23RADBNo ROA
45.6.202.0/24RADBNo ROA
45.6.203.0/24RADBNo ROA
2804:3cf8::/32ALTDB, RADB, TCNo ROA
2804:3cf8::/33RADBNo ROA
2804:3cf8:8000::/33RADBNo ROA

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.