bgpreport

Network · data from 2026-11-12

AS269532 P M - SERVICOS DE COMUNICACAO MULTIMIDIA

Registry name: AS269532 - ROUTINGER INTERNET E TI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269532, 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.188.140.0/23 Valid Other IRR onlyRADB 671 100% 66
45.188.143.0/24 Valid Other IRR onlyRADB 668 99% 66
2804:6614::/34 Valid Other IRR onlyRADB 636 100% 67
2804:6614:8000::/34 Valid Other IRR onlyRADB 636 100% 67
45.188.142.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:6614:4000::/34 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS269532'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 13 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR45.188.140.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.143.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:6614::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:6614:8000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR45.188.142.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:6614:4000::/34Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

45.188.140.0/22RADB, TCNo ROA
45.188.140.0/24RADBValid
45.188.141.0/24RADBValid
45.188.142.0/23RADBValid
2804:6614::/32RADB, TCValid
2804:6614::/33RADBValid
2804:6614:8000::/33RADBValid

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.