bgpreport

Network · data from 2026-11-12

AS271970 AS271970 - FIBERTEC SRL

Registry name: AS271970 - FIBERTEC SRL, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271970, 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.
131.196.188.0/24 Valid Nonecovered by 131.196.188.0/22 672 100% 67
131.196.189.0/24 Valid Nonecovered by 131.196.188.0/22 672 100% 67
131.196.190.0/24 Valid Nonecovered by 131.196.188.0/22 672 100% 67
131.196.191.0/24 Valid Nonecovered by 131.196.188.0/22 672 100% 67
2803:dbc0:202::/48 Valid Nonecovered by 2803:dbc0::/32 633 100% 67
2803:dbc0:500::/48 Valid Nonecovered by 2803:dbc0::/32 633 100% 67
131.196.188.0/22 Valid RIR databaseLACNIC 670 100% 67
2803:dbc0::/32 Valid RIR databaseLACNIC 633 100% 69

AS-SET

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

  • Route object: none6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none131.196.188.0/24No route object for it. A route object for 131.196.188.0/22 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.672 of 673
Route object: none131.196.189.0/24No route object for it. A route object for 131.196.188.0/22 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.672 of 673
Route object: none131.196.190.0/24No route object for it. A route object for 131.196.188.0/22 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.672 of 673
Route object: none131.196.191.0/24No route object for it. A route object for 131.196.188.0/22 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.672 of 673
Route object: none2803:dbc0:202::/48No route object for it. A route object for 2803:dbc0::/32 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.633 of 636
Route object: none2803:dbc0:500::/48No route object for it. A route object for 2803:dbc0::/32 with origin AS271970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271970 in the RIR database for the space.633 of 636

Route objects not announced

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

131.196.36.0/22RADBValid
170.83.108.0/22LACNICValid
190.103.84.0/22LACNICValid
2800:d00::/32LACNICValid

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.