bgpreport

Network · data from 2026-11-12

AS141574 St Broadband Cable Service

Registry name: STBROADP-AS - St Broadband Cable Service, IN · PeeringDB

3IPv4 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
1Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS141574, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141574, 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.210.0/24 Valid RIR databaseAPNIC 669 99% 66
103.160.211.0/24 Valid RIR databaseAPNIC 669 99% 66
2406:f140::/32 Valid RIR databaseAPNIC 636 100% 70
103.160.210.0/23 Valid RIR databaseAPNIC 40 6%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS141574: AS141574:AS-STBROADP. 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 (AS141574 isn't in the set, or no route object for AS141574 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 objectsAS141574 in itNot covered
AS141574:AS-STBROADP APNIClists itself further down 4253 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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

2406:f140::/48APNICInvalid: maxLength
2406:f140:1::/48APNICInvalid: maxLength
2406:f140:2::/48APNICInvalid: maxLength
2406:f140:3::/48APNICInvalid: maxLength
2406:f140:4::/48APNICInvalid: maxLength
2406:f140:5::/48APNICInvalid: maxLength
2406:f140:6::/48APNICInvalid: maxLength
2406:f140:7::/48APNICInvalid: maxLength
2406:f140:8::/48APNICInvalid: maxLength
2406:f140:9::/48APNICInvalid: maxLength
2406:f140:a::/48APNICInvalid: maxLength
2406:f140:b::/48APNICInvalid: maxLength
2406:f140:c::/48APNICInvalid: maxLength
2406:f140:d::/48APNICInvalid: maxLength
2406:f140:e::/48APNICInvalid: maxLength
2406:f140:f::/48APNICInvalid: maxLength

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.