bgpreport

Network · data from 2026-11-12

AS273976 FICOM INTERNATIONAL

Registry name: AS273976 - FICOM TELECOMUNICACIONES S.A.C., PE · PeeringDB

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

Announced routes

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

2803:b0d0::/48 No ROA Nonecovered by 2803:b0d0::/32 636 100% 67
2803:b0d0:5f00::/40 No ROA Nonecovered by 2803:b0d0::/32 635 100% 67
38.252.217.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
2803:b0d0::/32 No ROA Other IRR onlyALTDB 636 100% 67
2803:b0d0:fc00::/40 No ROA Other IRR onlyALTDB 636 100% 67
2803:b0d0:ff00::/40 No ROA Other IRR onlyALTDB 635 100% 67
190.93.224.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
190.93.224.0/23 Valid Other IRR onlyRADB 672 100% 66
190.93.224.0/24 Valid Other IRR onlyRADB 672 100% 66
190.93.225.0/24 Valid Other IRR onlyRADB 672 100% 66
190.93.226.0/23 Valid Other IRR onlyRADB 672 100% 66
190.93.226.0/24 Valid Other IRR onlyRADB 672 100% 66
190.93.227.0/24 Valid Other IRR onlyRADB 672 100% 67
170.62.156.0/23 Valid Other IRR onlyALTDB 671 100% 66
45.166.72.0/24 Valid RIR databaseALTDB, LACNIC, RADB 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS273976: AS273976. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273976 isn't in the set, or no route object for AS273976 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS273976 in itNot covered
AS273976 A single AS number, not a set: AS273976 (this network), 17 route objects.

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

  • ROA: none6
  • Route object: none2
  • Route object: RIR12
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2803:b0d0::/48No ROA covers it. Add a ROA for AS273976, maxLength 48.636 of 636
Route object: none2803:b0d0::/48No route object for it. A route object for 2803:b0d0::/32 with origin AS273976 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273976 in the RIR database for the space.636 of 636
ROA: none2803:b0d0:5f00::/40No ROA covers it. Add a ROA for AS273976, maxLength 40.635 of 636
Route object: none2803:b0d0:5f00::/40No route object for it. A route object for 2803:b0d0::/32 with origin AS273976 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273976 in the RIR database for the space.635 of 636
ROA: none38.252.217.0/24No ROA covers it. Add a ROA for AS273976, maxLength 24.672 of 673
Route object: RIR38.252.217.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2803:b0d0::/32No ROA covers it. Add a ROA for AS273976, maxLength 32.636 of 636
Route object: RIR2803:b0d0::/32Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none2803:b0d0:fc00::/40No ROA covers it. Add a ROA for AS273976, maxLength 40.636 of 636
Route object: RIR2803:b0d0:fc00::/40Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none2803:b0d0:ff00::/40No ROA covers it. Add a ROA for AS273976, maxLength 40.635 of 636
Route object: RIR2803:b0d0:ff00::/40Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR190.93.224.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.224.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.224.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.226.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.227.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.62.156.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

38.252.215.0/24RADBNo ROA
170.62.156.0/22ARIN, RADBValid
209.45.20.0/24LACNICValid
2803:a850::/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.