bgpreport

Network · data from 2026-11-12

AS9288 DBTECHNOLOGIES-AS-AP

Registry name: DBTECHNOLOGIES-AS-AP - Akhtaruzzaman t/a DB Technologies, BD · PeeringDB

14IPv4 routes 71.4% RPKI valid · 71.4% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
0No ROA 4 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS9288, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9288, 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.90.212.0/23 Invalid: maxLength Nonecovered by 103.90.212.0/22 8 1%low visibility 4
103.90.214.0/23 Invalid: maxLength Nonecovered by 103.90.212.0/22 8 1%low visibility 4
123.253.0.0/23 Invalid: maxLength Nonecovered by 123.253.0.0/22 8 1%low visibility 4
123.253.2.0/23 Invalid: maxLength Nonecovered by 123.253.0.0/22 8 1%low visibility 4
103.90.212.0/22 Valid RIR databaseAPNIC 672 100% 67
123.253.1.0/24 Valid RIR databaseAPNIC 672 100% 67
103.90.212.0/24 Valid RIR databaseAPNIC 670 100% 68
103.90.213.0/24 Valid RIR databaseAPNIC 670 100% 68
103.90.214.0/24 Valid RIR databaseAPNIC 670 100% 68
103.90.215.0/24 Valid RIR databaseAPNIC 670 100% 68
123.253.0.0/24 Valid RIR databaseAPNIC 670 100% 68
123.253.2.0/24 Valid RIR databaseAPNIC 670 100% 68
123.253.3.0/24 Valid RIR databaseAPNIC 670 100% 68
123.253.0.0/22 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS9288: APNIC::AS9288:AS-DBTECH. 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 (AS9288 isn't in the set, or no route object for AS9288 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 objectsAS9288 in itNot covered
APNIC::AS9288:AS-DBTECH APNIC 1117 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 15 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.90.212.0/23ROA 103.90.212.0/22 AS9288 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.90.212.0/23.8 of 673
Route object: none103.90.212.0/23No route object for it. A route object for 103.90.212.0/22 with origin AS9288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9288 in the RIR database for the space.8 of 673
ROA: maxLength103.90.214.0/23ROA 103.90.212.0/22 AS9288 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.90.214.0/23.8 of 673
Route object: none103.90.214.0/23No route object for it. A route object for 103.90.212.0/22 with origin AS9288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9288 in the RIR database for the space.8 of 673
ROA: maxLength123.253.0.0/23ROA 123.253.0.0/22 AS9288 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 123.253.0.0/23.8 of 673
Route object: none123.253.0.0/23No route object for it. A route object for 123.253.0.0/22 with origin AS9288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9288 in the RIR database for the space.8 of 673
ROA: maxLength123.253.2.0/23ROA 123.253.0.0/22 AS9288 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 123.253.2.0/23.8 of 673
Route object: none123.253.2.0/23No route object for it. A route object for 123.253.0.0/22 with origin AS9288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9288 in the RIR database for the space.8 of 673

Route objects not announced

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

202.123.96.0/20RADBNo ROA
203.16.65.0/24RADBNo ROA
203.16.178.0/23RADBNo ROA
203.30.62.0/23RADBNo ROA
203.30.63.0/24RADBNo ROA
203.56.189.0/24RADBNo ROA
203.56.190.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.