Network · data from 2026-11-12
AS18568 Bidtellect
Registry name: BIDTELLECT - Bidtellect Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18568, 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.
| 192.132.32.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 64.38.118.0/23 | No ROA | Other IRR onlyRADB | 664 99% |
AS-SET
PeeringDB's irr_as_set for AS18568: RADB::AS-BIDTELLECT. 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 (AS18568 isn't in the set, or no route object for AS18568 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 | AS18568 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-BIDTELLECT | RADB | 1 | 1 | 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 8 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.132.32.0/23 | No ROA covers it. Add a ROA for AS18568, maxLength 23. |
| Route object: RIR | 192.132.32.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 64.38.118.0/23 | No ROA covers it. Add a ROA for AS18568, maxLength 23. |
| Route object: RIR | 64.38.118.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18568 whose prefix no peer sees AS18568 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.38.118.0/24 | RADB | No ROA |
| 64.38.119.0/24 | RADB | No ROA |
| 192.132.32.0/24 | RADB | No ROA |
| 192.132.33.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.