Network · data from 2026-11-12
AS26415 VeriSign Global Registry Services
Registry name: VERISIGN-INC - VeriSign Global Registry Services, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26415, 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.
| 144.208.212.160/28 | Invalid: origin | None | 1 0%low visibility |
| 199.7.63.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 2a00:11c0:48:5::/64 | Valid | None | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS26415: AS-GTLD. 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 (AS26415 isn't in the set, or no route object for AS26415 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 | AS26415 in it | Not covered |
|---|---|---|---|---|---|
| AS-GTLD | RADB | 224 | 1 | Yes | 2 |
| ARIN (also) | 224 | 1 | Yes | 2 |
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 8 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 144.208.212.160/28 | ROAs covering it name AS42473, not AS26415. If AS26415 should announce it, add a ROA for AS26415. |
| Route object: none | 144.208.212.160/28 | No route object for it. Add a route object with origin AS26415 in the RIR database for the space. |
| ROA: none | 199.7.63.0/24 | No ROA covers it. Add a ROA for AS26415, maxLength 24. |
| Route object: none | 2a00:11c0:48:5::/64 | No route object for it. Add a route object with origin AS26415 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26415 whose prefix no peer sees AS26415 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.33.14.0/24 | ARIN, RADB | Valid |
| 192.58.128.0/24 | ARIN, RADB | Valid |
| 2001:503:c27::/48 | ARIN, RADB | Valid |
| 2001:503:231d::/48 | ARIN, RADB | 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.