Network · data from 2026-11-12
AS7598 Forcepoint - APAC
Registry name: FUL-APAC-AS - Forcepoint UK Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7598, 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.
| 116.50.57.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 4 1%low visibility |
| 116.50.60.0/24 | No ROA | RIR databaseAPNIC, RADB | 4 1%low visibility |
| 2400:5e00::/32 | No ROA | RIR databaseAPNIC, NTTCOM | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS7598: AS-WHS-AP. 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 (AS7598 isn't in the set, or no route object for AS7598 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 | AS7598 in it | Not covered |
|---|---|---|---|---|---|
| AS-WHS-AP | RADB | 2 | 2 | Yes | 0 |
| RIPE (also) | 2 | 2 | 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 13 are in fix.csv.
- ROA: none3
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 116.50.57.0/24 | No ROA covers it. Add a ROA for AS7598, maxLength 24. |
| ROA: none | 116.50.60.0/24 | No ROA covers it. Add a ROA for AS7598, maxLength 24. |
| ROA: none | 2400:5e00::/32 | No ROA covers it. Add a ROA for AS7598, maxLength 32. |
Route objects not announced
Route objects with origin AS7598 whose prefix no peer sees AS7598 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 116.50.56.0/21 | APNIC | No ROA |
| 116.50.56.0/24 | APNIC, RADB | No ROA |
| 116.50.58.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 116.50.59.0/24 | APNIC, RADB | No ROA |
| 116.50.61.0/24 | APNIC, RADB | No ROA |
| 116.50.62.0/24 | APNIC | No ROA |
| 116.50.63.0/24 | APNIC | No ROA |
| 202.161.116.0/24 | RADB | No ROA |
| 203.62.180.0/22 | RADB | No ROA |
| 203.62.183.0/24 | RADB | No 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.