bgpreport

Network · data from 2026-11-12

AS33403 HEIYO-TELECOM - HEIYO CLOUD CORP.

Registry name: HEIYO-TELECOM - HEIYO CLOUD CORP., US · not in PeeringDB

4IPv4 routes 75.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS33403, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33403, 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.
128.254.242.0/24 No ROA RIR databaseARIN, RADB 670 100% 67
144.225.78.0/24 Valid Nonecovered by 144.225.78.0/23 606 90% 67
144.225.79.0/24 Valid Nonecovered by 144.225.78.0/23 606 90% 67
144.225.78.0/23 Valid RIR databaseARIN, RADB 91 14% 37

AS-SET

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

  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none128.254.242.0/24No ROA covers it. Add a ROA for AS33403, maxLength 24.670 of 673
Route object: none144.225.78.0/24No route object for it. A route object for 144.225.78.0/23 with origin AS33403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33403 in the RIR database for the space.606 of 673
Route object: none144.225.79.0/24No route object for it. A route object for 144.225.78.0/23 with origin AS33403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33403 in the RIR database for the space.606 of 673

Route objects not announced

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

128.254.240.0/22RADBNo ROA
128.254.242.0/23ARINNo ROA
128.254.243.0/24ARIN, RADBNo 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.