bgpreport

Network · data from 2026-11-12

AS268191 AS268191 - MARTINS TELECOM

Registry name: AS268191 - MARTINS TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268191, 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.
177.86.230.0/24 No ROA Nonecovered by 177.86.228.0/22 671 100% 66
177.86.228.0/24 No ROA Nonecovered by 177.86.228.0/22 667 99% 67
177.86.229.0/24 No ROA Nonecovered by 177.86.228.0/22 666 99% 67
177.86.224.0/23 Valid Nonecovered by 177.86.224.0/22 667 99% 67
45.235.176.0/22 Valid Other IRR onlyRADB 672 100% 66
45.235.176.0/24 Valid Other IRR onlyRADB 672 100% 66
45.235.177.0/24 Valid Other IRR onlyRADB 672 100% 66
45.235.178.0/24 Valid Other IRR onlyRADB 672 100% 66
45.235.179.0/24 Valid Other IRR onlyRADB 672 100% 66
2804:4d58::/32 Valid Other IRR onlyRADB 634 100% 70
2804:4d58:4800::/39 Valid Other IRR onlyRADB 634 100% 70
2804:4d58:4a00::/39 Valid Other IRR onlyRADB 634 100% 70

AS-SET

AS268191 isn't in PeeringDB, where networks name their 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 20 are in fix.csv.

  • ROA: none3
  • Route object: none4
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none177.86.230.0/24No ROA covers it. Add a ROA for AS268191, maxLength 24.671 of 673
Route object: none177.86.230.0/24No route object for it. A route object for 177.86.228.0/22 with origin AS268191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268191 in the RIR database for the space.671 of 673
ROA: none177.86.228.0/24No ROA covers it. Add a ROA for AS268191, maxLength 24.667 of 673
Route object: none177.86.228.0/24No route object for it. A route object for 177.86.228.0/22 with origin AS268191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268191 in the RIR database for the space.667 of 673
ROA: none177.86.229.0/24No ROA covers it. Add a ROA for AS268191, maxLength 24.666 of 673
Route object: none177.86.229.0/24No route object for it. A route object for 177.86.228.0/22 with origin AS268191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268191 in the RIR database for the space.666 of 673
Route object: none177.86.224.0/23No route object for it. A route object for 177.86.224.0/22 with origin AS268191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268191 in the RIR database for the space.667 of 673
Route object: RIR45.235.176.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.235.176.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.235.177.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.235.178.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.235.179.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:4d58::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4d58:4800::/39Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4d58:4a00::/39Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.235.176.0/23RADBValid
45.235.178.0/23RADBValid
177.86.224.0/22RADBValid
177.86.228.0/22RADBNo ROA
177.86.231.0/24RADBNo 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.