bgpreport

Network · data from 2026-11-12

AS142271 EWS DS Networks Inc

Registry name: DOUBLESQUARE-AS-AP - EWS DS Networks Inc, PH · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
6Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS142271, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS142271, 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.94.78.0/23 Valid Other IRR onlyRADB 672 100% 67
154.18.197.0/24 Valid Other IRR onlyRADB 16 2%low visibility 11
103.94.78.0/24 Valid Other IRR onlyRADB 15 2%low visibility 11
103.94.79.0/24 Valid Other IRR onlyRADB 15 2%low visibility 11
154.18.196.0/24 Valid Other IRR onlyRADB 15 2%low visibility 11
103.167.66.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.186.138.0/23 Valid RIR databaseAPNIC 672 100% 67
154.18.196.0/23 Valid RIR databaseARIN, RADB 672 100% 67
2400:c3e0::/32 Valid RIR databaseAPNIC 636 100% 69
103.186.138.0/24 Valid RIR databaseAPNIC 15 2%low visibility 11
103.186.139.0/24 Valid RIR databaseAPNIC 15 2%low visibility 11

AS-SET

PeeringDB's irr_as_set for AS142271: AS142271:AS-CUSTOMER. 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 (AS142271 isn't in the set, or no route object for AS142271 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 objectsAS142271 in itNot covered
AS142271:AS-CUSTOMER APNIClists itself further down1 member set in no database: AS150786:AS-CUSTOMERS 1721535,337 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.

  • Route object: RIR5
  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR103.94.78.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR154.18.197.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673
Route object: RIR103.94.78.0/24Route object only in RADB. Add it in the RIR database for the space.15 of 673
Route object: RIR103.94.79.0/24Route object only in RADB. Add it in the RIR database for the space.15 of 673
Route object: RIR154.18.196.0/24Route object only in RADB. Add it in the RIR database for the space.15 of 673
AS-SET: missing memberAS142271:AS-CUSTOMERAS142271:AS-CUSTOMER (APNIC) lists AS150786:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

2a10:2f01:2a5::/48RIPENo ROA
2a13:9500:140::/48RIPEValid

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.