bgpreport

Network · data from 2026-11-12

AS262688 HOST TECNOLOGIA

Registry name: AS262688 - MHNET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262688, 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.
186.236.32.0/22 Valid Nonecovered by 186.236.32.0/20 671 100% 67
200.229.176.0/24 Valid Nonecovered by 200.229.176.0/20 670 100% 67
2804:310:8000::/33 Valid Nonecovered by 2804:310::/32 633 100% 67
177.154.96.0/20 Valid Other IRR onlyRADB 671 100% 67
179.127.224.0/20 Valid Other IRR onlyRADB 671 100% 67
186.236.32.0/20 Valid Other IRR onlyRADB 671 100% 67
186.236.32.0/23 Valid Other IRR onlyRADB 671 100% 67
186.236.34.0/23 Valid Other IRR onlyRADB 671 100% 67
187.87.208.0/20 Valid Other IRR onlyRADB 671 100% 67
200.229.176.0/20 Valid Other IRR onlyRADB 670 100% 67

AS-SET

AS262688'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 25 are in fix.csv.

  • Route object: none3
  • Route object: RIR7
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none186.236.32.0/22No route object for it. A route object for 186.236.32.0/20 with origin AS262688 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262688 in the RIR database for the space.671 of 673
Route object: none200.229.176.0/24No route object for it. A route object for 200.229.176.0/20 with origin AS262688 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262688 in the RIR database for the space.670 of 673
Route object: none2804:310:8000::/33No route object for it. A route object for 2804:310::/32 with origin AS262688 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262688 in the RIR database for the space.633 of 636
Route object: RIR177.154.96.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR179.127.224.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.236.32.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.236.32.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.236.34.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.87.208.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.229.176.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

186.236.36.0/23RADBValid
186.236.38.0/23RADBValid
186.236.40.0/23RADBValid
186.236.42.0/23RADBValid
187.87.208.0/23RADBValid
187.87.210.0/23RADBValid
187.87.212.0/23RADBValid
187.87.214.0/23RADBValid
187.87.216.0/23RADBValid
187.87.218.0/23RADBValid
187.87.220.0/23RADBValid
187.87.222.0/23RADBValid
2804:310::/32RADBValid
2804:310:2::/48RADBValid
2804:310:b000::/36RADBValid

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.