bgpreport

Network · data from 2026-11-12

AS262879 Hifive Provedor de Internet

Registry name: AS262879 - Hifive Provedor de Internet Ltda, BR · PeeringDB

16IPv4 routes 0.0% RPKI valid · 18.8% with a route object
0IPv6 routes
13RPKI invalid 13 origin · 0 maxLength
3No ROA 13 with no route object for this origin
16Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS262879, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262879, 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.21.208.0/24 Invalid: origin Other origin onlycovered by 177.21.208.0/22 0 0%low visibility 1
177.21.209.0/24 Invalid: origin Other origin onlycovered by 177.21.208.0/22 0 0%low visibility 1
177.21.210.0/24 Invalid: origin Other origin onlycovered by 177.21.208.0/22 0 0%low visibility 1
177.21.212.0/24 Invalid: origin Other origin onlycovered by 177.21.212.0/22 0 0%low visibility 1
177.21.213.0/24 Invalid: origin Other origin onlycovered by 177.21.212.0/22 0 0%low visibility 1
177.21.214.0/24 Invalid: origin Other origin onlycovered by 177.21.212.0/22 0 0%low visibility 1
177.21.215.0/24 Invalid: origin Other origin onlycovered by 177.21.212.0/22 0 0%low visibility 1
177.21.218.0/24 Invalid: origin Other origin onlycovered by 177.21.216.0/21 0 0%low visibility 1
177.21.219.0/24 Invalid: origin Other origin onlycovered by 177.21.216.0/21 0 0%low visibility 1
177.21.220.0/24 Invalid: origin Nonecovered by 177.21.216.0/21 0 0%low visibility 1
177.21.221.0/24 Invalid: origin Nonecovered by 177.21.216.0/21 0 0%low visibility 1
177.21.222.0/24 Invalid: origin Nonecovered by 177.21.222.0/23 0 0%low visibility 1
177.21.223.0/24 Invalid: origin Other origin onlycovered by 177.21.222.0/23 0 0%low visibility 1
177.21.211.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1
177.21.216.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1
177.21.217.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1

AS-SET

AS262879'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 43 are in fix.csv.

  • ROA: origin13
  • ROA: none3
  • Route object: none13
  • Route object: RIR3
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: origin177.21.208.0/24ROAs covering it name AS273443, not AS262879; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.208.0/24Route objects for it name AS273443. A route object for 177.21.208.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.209.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.209.0/24Route objects for it name AS273443. A route object for 177.21.208.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.210.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.210.0/24Route objects for it name AS273443. A route object for 177.21.208.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.212.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.212.0/24Route objects for it name AS273443. A route object for 177.21.212.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.213.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.213.0/24Route objects for it name AS273443. A route object for 177.21.212.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.214.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.214.0/24Route objects for it name AS273443. A route object for 177.21.212.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.215.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.215.0/24Route objects for it name AS273443. A route object for 177.21.212.0/22 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.218.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.218.0/24Route objects for it name AS273443. A route object for 177.21.216.0/21 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.219.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.219.0/24Route objects for it name AS273443. A route object for 177.21.216.0/21 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.220.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.220.0/24No route object for it. A route object for 177.21.216.0/21 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.221.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.221.0/24No route object for it. A route object for 177.21.216.0/21 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.222.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.222.0/24No route object for it. A route object for 177.21.222.0/23 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: origin177.21.223.0/24ROAs covering it name AS273443, not AS262879. If AS262879 should announce it, add a ROA for AS262879.0 of 673
Route object: none177.21.223.0/24Route objects for it name AS273443. A route object for 177.21.222.0/23 with origin AS262879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262879 in the RIR database for the space.0 of 673
ROA: none177.21.211.0/24No ROA covers it. Add a ROA for AS262879, maxLength 24.0 of 673
Route object: RIR177.21.211.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673
ROA: none177.21.216.0/24No ROA covers it. Add a ROA for AS262879, maxLength 24.0 of 673
Route object: RIR177.21.216.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673
ROA: none177.21.217.0/24No ROA covers it. Add a ROA for AS262879, maxLength 24.0 of 673
Route object: RIR177.21.217.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

170.245.140.0/22RADBNo ROA
177.21.208.0/20NTTCOM, RADBNo ROA
177.21.208.0/21RADBNo ROA
177.21.208.0/22RADBNo ROA
177.21.212.0/22RADBNo ROA
177.21.216.0/21RADBNo ROA
177.21.216.0/23RADBNo ROA
177.21.222.0/23RADBNo ROA
2804:5b4::/32RADBNo ROA
2804:5b4::/33RADBNo ROA
2804:5b4:8000::/33RADBNo 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.