bgpreport

Network · data from 2026-11-12

AS141676 St. Joseph Cable TV System

Registry name: SJCTS-AS-AP - St. Joseph Cable TV System, PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141676, 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.187.0/24 Invalid: maxLength Nonecovered by 143.20.186.0/23 10 1%low visibility 9
103.161.240.0/23 Valid RIR databaseAPNIC 673 100% 68
103.161.240.0/24 Valid RIR databaseAPNIC 673 100% 69
103.161.241.0/24 Valid RIR databaseAPNIC 673 100% 69
143.20.186.0/23 Valid RIR databaseRADB, RIPE 673 100% 68
2001:df5:d680::/48 Valid RIR databaseAPNIC 636 100% 69
2400:78a0::/32 Valid RIR databaseAPNIC 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS141676: AS141676:AS-ALL. 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 (AS141676 isn't in the set, or no route object for AS141676 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 objectsAS141676 in itNot covered
AS141676:AS-ALL APNIC 1134 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 30 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: maxLength143.20.187.0/24ROA 143.20.186.0/23 AS141676 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 143.20.187.0/24.10 of 673
Route object: none143.20.187.0/24No route object for it. A route object for 143.20.186.0/23 with origin AS141676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141676 in the RIR database for the space.10 of 673

Route objects not announced

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

2400:78a0::/36APNICValid
2400:78a0::/40APNICValid
2400:78a0::/44APNICValid
2400:78a0::/48APNICValid
2400:78a0:10::/44APNICValid
2400:78a0:1000::/36APNICValid
2400:78a0:1000::/40APNICValid
2400:78a0:1100::/40APNICValid
2400:78a0:1100::/44APNICValid
2400:78a0:1110::/44APNICValid
2400:78a0:1110::/47APNICValid
2400:78a0:1112::/47APNICValid
2400:78a0:1114::/47APNICValid
2400:78a0:1116::/47APNICValid
2400:78a0:1118::/47APNICValid
2400:78a0:111a::/47APNICValid
2400:78a0:111c::/47APNICValid
2400:78a0:111e::/47APNICValid
2400:78a0:1120::/44APNICValid
2400:78a0:1120::/47APNICValid
2400:78a0:1122::/47APNICValid
2400:78a0:1124::/47APNICValid
2400:78a0:1126::/47APNICValid
2400:78a0:1128::/47APNICValid
2400:78a0:112a::/47APNICValid
2400:78a0:112c::/47APNICValid
2400:78a0:112e::/47APNICValid
2400:78a0:1200::/40APNICValid

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.