bgpreport

Network · data from 2026-11-12

AS17644 ZORN-AS-AP

Registry name: IOT-AS-AP - IoT Techsmart Pte. Ltd., BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17644, 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.
2001:df5:f9c0::/48 Invalid: origin Other origin only 103 16% 43
103.14.23.0/24 Valid RIR databaseAPNIC 673 100% 69
163.128.216.0/24 Valid RIR databaseAPNIC 673 100% 70
165.99.165.0/24 Valid RIR databaseAPNIC 673 100% 69
160.25.226.0/24 Valid RIR databaseAPNIC 672 100% 68
163.128.217.0/24 Valid RIR databaseAPNIC 669 99% 67
2001:df3:ad40::/48 Valid RIR databaseAPNIC 635 100% 70
2001:df4:13c0::/48 Valid RIR databaseAPNIC 635 100% 69
2001:df4:8440::/48 Valid RIR databaseAPNIC 635 100% 69
2402:5720::/32 Valid RIR databaseAPNIC 635 100% 69
2402:6520::/32 Valid RIR databaseAPNIC 635 100% 69
2001:df3:ad41::/48 Valid RIR databaseAPNIC 634 100% 69
2001:df4:13c1::/48 Valid RIR databaseAPNIC 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS17644: APNIC::AS17644:AS-CUSTOMERS. 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 (AS17644 isn't in the set, or no route object for AS17644 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 objectsAS17644 in itNot covered
APNIC::AS17644:AS-CUSTOMERS APNIC 11480 No 13

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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2001:df5:f9c0::/48ROAs covering it name AS147180, AS152698, not AS17644. If AS17644 should announce it, add a ROA for AS17644.103 of 636
Route object: none2001:df5:f9c0::/48Route objects for it name AS147180, AS152698. Add a route object with origin AS17644 in the RIR database for the space.103 of 636
AS-SET: own ASNAPNIC::AS17644:AS-CUSTOMERSAS17644 isn't in AS17644:AS-CUSTOMERS (APNIC) once expanded. Add AS17644 to it.

Route objects not announced

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

2001:df4:8441::/48APNICValid
2001:df6:5941::/48APNICValid
2402:5720:f000::/44APNICValid

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.