bgpreport

Network · data from 2026-11-12

AS273417 AS273417 - INFORTEC SERVICOS DE COMUNICACOES LTDA

Registry name: AS273417 - INFORTEC SERVICOS DE COMUNICACOES LTDA, BR · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 routes 100.0% RPKI valid · 14.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
0Route objects not announced registered with origin AS273417, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273417, 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.
2804:8e50::/33 Valid Nonecovered by 2804:8e50::/32 634 100% 67
2804:8e50::/34 Valid Nonecovered by 2804:8e50::/32 634 100% 67
2804:8e50:4000::/34 Valid Nonecovered by 2804:8e50::/32 634 100% 67
2804:8e50:8000::/33 Valid Nonecovered by 2804:8e50::/32 634 100% 67
2804:8e50:8000::/34 Valid Nonecovered by 2804:8e50::/32 634 100% 67
2804:8e50:c000::/34 Valid Nonecovered by 2804:8e50::/32 634 100% 67
138.94.215.0/24 Valid Other IRR onlyTC 671 100% 67
187.86.163.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:8e50::/32 Valid Other IRR onlyRADB, TC 635 100% 70
38.224.227.0/24 Valid RIR databaseARIN 668 99% 66

AS-SET

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

  • Route object: none6
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2804:8e50::/33No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: none2804:8e50::/34No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: none2804:8e50:4000::/34No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: none2804:8e50:8000::/33No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: none2804:8e50:8000::/34No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: none2804:8e50:c000::/34No route object for it. A route object for 2804:8e50::/32 with origin AS273417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273417 in the RIR database for the space.634 of 636
Route object: RIR138.94.215.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.86.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:8e50::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS273417 is announced.

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.