Network · data from 2026-11-12
AS55651 DBolical Pty Ltd
Registry name: DBOLICALPTYLTD-AU - DBOLICAL PTY LTD, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55651, 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.24.120.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.24.121.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.24.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 103.24.123.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2406:bd00:de00::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2406:bd00:de50::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2406:bd00:decd::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS55651's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS55651 is announced.
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.