Network · data from 2026-11-12
AS150369 TelHi Corporation
Registry name: Infal - TelHi Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150369, 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.
| 103.26.26.0/23 | Valid | Other IRR onlyJPIRR | 669 99% |
| 2401:2d60::/32 | Valid | Other IRR onlyJPIRR | 634 100% |
| 103.151.154.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 2602:fd6f:1a::/48 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS150369: AS150369:AS-TELHI. 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 (AS150369 isn't in the set, or no route object for AS150369 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.
| Name | Database | ASNs | Sets | AS150369 in it | Not covered |
|---|---|---|---|---|---|
| AS150369:AS-TELHI | JPIRRlists itself further down1 member set in no database: AS-CIRCLE | 50 | 20 | Yes | 0 |
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.
- Route object: RIR2
- AS-SET: missing member1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.26.26.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:2d60::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| AS-SET: missing member | AS150369:AS-TELHI | AS150369:AS-TELHI (JPIRR) lists AS-CIRCLE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS150369 whose prefix no peer sees AS150369 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.204.5.0/24 | ARIN, RADB | Valid |
| 2401:2d60::/33 | JPIRR | Valid |
| 2a13:9500:1d8::/48 | RIPE | Valid |
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.