bgpreport

Network · data from 2026-11-12

AS269495 FibraMania Serviços de Telecomunicações

Registry name: AS269495 - FibraMania Servicos de Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269495, 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.187.145.0/24 Valid Nonecovered by 45.187.144.0/23 672 100% 67
45.187.146.0/24 Valid Nonecovered by 45.187.146.0/23 667 99% 67
45.187.147.0/24 Valid Nonecovered by 45.187.146.0/23 665 99% 67
2804:6580:c000::/34 Valid Nonecovered by 2804:6580::/32 635 100% 67
2804:6580:8000::/34 Valid Nonecovered by 2804:6580::/32 634 100% 67
45.187.144.0/24 Valid Nonecovered by 45.187.144.0/23 2 0%low visibility 2

AS-SET

AS269495'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 11 are in fix.csv.

  • Route object: none6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none45.187.145.0/24No route object for it. A route object for 45.187.144.0/23 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.672 of 673
Route object: none45.187.146.0/24No route object for it. A route object for 45.187.146.0/23 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.667 of 673
Route object: none45.187.147.0/24No route object for it. A route object for 45.187.146.0/23 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.665 of 673
Route object: none2804:6580:c000::/34No route object for it. A route object for 2804:6580::/32 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.635 of 636
Route object: none2804:6580:8000::/34No route object for it. A route object for 2804:6580::/32 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.634 of 636
Route object: none45.187.144.0/24No route object for it. A route object for 45.187.144.0/23 with origin AS269495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269495 in the RIR database for the space.2 of 673

Route objects not announced

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

45.187.144.0/22RADBValid
45.187.144.0/23RADBValid
45.187.146.0/23RADBValid
2804:6580::/32RADBValid
2804:6580::/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.