bgpreport

Network · data from 2026-11-12

AS141199 Century Link Plus Co

Registry name: CLPC-AS-AP - Century Link Plus, MM · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141199, 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.160.146.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66

AS-SET

PeeringDB's irr_as_set for AS141199: AS141199:AS-SET-CLPC. 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 (AS141199 isn't in the set, or no route object for AS141199 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 objectsAS141199 in itNot covered
AS141199:AS-SET-CLPC APNIC 010 No 1

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 11 are in fix.csv.

  • AS-SET: own ASN1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS141199:AS-SET-CLPCAS141199 isn't in AS141199:AS-SET-CLPC (APNIC) once expanded. Add AS141199 to it.

Route objects not announced

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

165.101.48.0/24APNIC, RADBValid
165.101.48.0/25APNICValid
165.101.48.128/25APNICValid
2001:df1:ea40::/48APNIC, RADBValid
2001:df1:ea40::/49APNICValid
2001:df1:ea40::/50APNICValid
2001:df1:ea40:4000::/50APNICValid
2001:df1:ea40:8000::/49APNICValid
2001:df1:ea40:8000::/50APNICValid
2001:df1:ea40:c000::/50APNICValid

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.