bgpreport

Network · data from 2026-11-12

AS273315 LIDER NET E SERVICOS DE MULTIMIDIA

Registry name: AS273315 - LIDER NET E SERVICOS DE MULTIMIDIA, BR · PeeringDB

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

Announced routes

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

2804:8cd0:500::/40 No ROA Nonecovered by 2804:8cd0::/33 634 100% 67
128.201.186.0/24 No ROA Other IRR onlyTC 671 100% 66
128.201.184.0/23 No ROA Other IRR onlyTC 669 99% 67
128.201.185.0/24 No ROA Other IRR onlyTC 669 99% 67
128.201.187.0/24 No ROA Other IRR onlyTC 669 99% 66
2804:8cd0::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS273315's PeeringDB record names no AS-SET.

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2804:8cd0:500::/40No ROA covers it. Add a ROA for AS273315, maxLength 40.634 of 636
Route object: none2804:8cd0:500::/40No route object for it. A route object for 2804:8cd0::/33 with origin AS273315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273315 in the RIR database for the space.634 of 636
ROA: none128.201.186.0/24No ROA covers it. Add a ROA for AS273315, maxLength 24.671 of 673
Route object: RIR128.201.186.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none128.201.184.0/23No ROA covers it. Add a ROA for AS273315, maxLength 23.669 of 673
Route object: RIR128.201.184.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none128.201.185.0/24No ROA covers it. Add a ROA for AS273315, maxLength 24.669 of 673
Route object: RIR128.201.185.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none128.201.187.0/24No ROA covers it. Add a ROA for AS273315, maxLength 24.669 of 673
Route object: RIR128.201.187.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:8cd0::/32No ROA covers it. Add a ROA for AS273315, maxLength 32.635 of 636
Route object: RIR2804:8cd0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

128.201.184.0/22TCNo ROA
128.201.184.0/24TCNo ROA
128.201.186.0/23TCNo ROA
2804:8cd0::/33TCNo ROA
2804:8cd0:8000::/33TCNo 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.