bgpreport

Network · data from 2026-11-12

AS17413 DODO-TW-ISP

Registry name: DODO-Core-TW - Dodo Ltd., TW · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
16IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS17413, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17413, 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.
160.250.98.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
2401:dae0::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:1000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:2000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:3000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:4000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:5000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:6000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:7000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:8000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:9000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:a000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:b000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:c000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:d000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:e000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
2401:dae0:f000::/36 Valid RIR databaseAPNIC, RADB 632 99% 69
160.250.98.0/24 Valid RIR databaseAPNIC 261 39% 60
160.250.99.0/24 Valid RIR databaseAPNIC 261 39% 60

AS-SET

PeeringDB's irr_as_set for AS17413: APNIC::AS17413:AS-DODOTW. 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 (AS17413 isn't in the set, or no route object for AS17413 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.

NameDatabaseASNsSets Route objectsAS17413 in itNot covered
APNIC::AS17413:AS-DODOTW APNIC 1120 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 1 are in fix.csv.

  • Route object: not announced1

Route objects not announced

Route objects with origin AS17413 whose prefix no peer sees AS17413 announce. Many are kept on purpose (backup routes, space announced only in some places).

61.67.113.0/24RADBNo 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.