bgpreport

Network · data from 2026-11-12

AS131677 OPENFOR

Registry name: OPENFOR - OpenFor Telecommunications Co., Ltd., TW · PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object
3IPv6 routes 100.0% RPKI valid · 66.7% 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 AS131677, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131677, 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.147.130.0/23 Valid Other origin only 671 100% 67
2405:b8c0::/32 Valid Other origin only 636 100% 67
103.149.64.0/23 Valid Other IRR onlyRADB 671 100% 67
103.152.252.0/23 Valid Other IRR onlyRADB 671 100% 67
2405:e4c0::/32 Valid Other IRR onlyRADB 636 100% 67
2406:3a40::/32 Valid Other IRR onlyRADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS131677: AS131677. 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 (AS131677 isn't in the set, or no route object for AS131677 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 objectsAS131677 in itNot covered
AS131677 A single AS number, not a set: AS131677 (this network), 4 route objects.

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.

  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none103.147.130.0/23Route objects for it name AS131674. Add a route object with origin AS131677 in the RIR database for the space.671 of 673
Route object: none2405:b8c0::/32Route objects for it name AS131674. Add a route object with origin AS131677 in the RIR database for the space.636 of 636
Route object: RIR103.149.64.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.152.252.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2405:e4c0::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2406:3a40::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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