bgpreport

Network · data from 2026-11-12

AS402782 Taipei Mobile (JP)

Registry name: AS-JPY - TAIPEI101, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402782, 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.
143.20.8.0/24 Valid Nonecovered by 143.20.8.0/23 669 99% 67
143.20.9.0/24 Valid Nonecovered by 143.20.8.0/23 669 99% 67
85.149.217.0/24 Valid RIR databaseRIPE 670 100% 67
143.20.8.0/23 Valid RIR databaseRADB, RIPE 670 100% 67
2602:faa8:659::/48 Valid RIR databaseARIN 635 100% 69
2602:faa8:ab0::/44 Valid RIR databaseARIN 635 100% 69
2602:faa8:800::/44 Valid RIR databaseARIN 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS402782: RIPE::AS-NOVEMBER. 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 (AS402782 isn't in the set, or no route object for AS402782 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 objectsAS402782 in itNot covered
RIPE::AS-NOVEMBER RIPE2 member sets in no database: AS-19890604, AS-LIBERALLY 10172 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 4 are in fix.csv.

  • Route object: none2
  • AS-SET: missing member2
ChangePrefix or setDetailFull-table peers
Route object: none143.20.8.0/24No route object for it. A route object for 143.20.8.0/23 with origin AS402782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402782 in the RIR database for the space.669 of 673
Route object: none143.20.9.0/24No route object for it. A route object for 143.20.8.0/23 with origin AS402782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402782 in the RIR database for the space.669 of 673
AS-SET: missing memberRIPE::AS-NOVEMBERAS-NOVEMBER (RIPE) lists AS-19890604; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NOVEMBERAS-NOVEMBER (RIPE) lists AS-LIBERALLY; no IRR database read has it.

Route objects not announced

Every route object with origin AS402782 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.