bgpreport

Network · data from 2026-11-12

AS133334 DCTV Cable Network Broadband Services

Registry name: DCNBSI-AS-AP - DCTV Cable Network Broadband Services Inc, PH · PeeringDB

8IPv4 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
0Low visibility seen by under 10% of full-table peers
38Route objects not announced registered with origin AS133334, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133334, 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.

2.58.228.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
45.124.56.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
103.31.72.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
103.61.220.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
103.197.84.0/22 Valid RIR databaseAPNIC 673 100% 69
103.200.32.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
103.203.52.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
103.225.136.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
2401:b80::/32 Valid RIR databaseAPNIC, RADB 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS133334: AS-DCTV-PH. 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 (AS133334 isn't in the set, or no route object for AS133334 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 objectsAS133334 in itNot covered
AS-DCTV-PH RADB 3156 Yes 0
APNIC (also) 3156 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 38 are in fix.csv.

  • Route object: not announced38

Route objects not announced

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

2.58.228.0/24APNIC, RADBValid
2.58.229.0/24APNIC, RADBValid
2.58.230.0/24APNIC, RADBValid
2.58.231.0/24APNIC, RADBValid
45.124.56.0/24APNIC, RADBValid
45.124.57.0/24APNIC, RADBValid
45.124.58.0/24APNIC, RADBValid
45.124.59.0/24APNIC, RADBValid
103.31.72.0/24APNIC, RADBValid
103.31.73.0/24APNIC, RADBValid
103.31.74.0/24APNIC, RADBValid
103.31.75.0/24APNIC, RADBValid
103.61.220.0/24APNIC, RADBValid
103.61.221.0/24APNIC, RADBValid
103.61.222.0/24APNIC, RADBValid
103.61.223.0/24APNIC, RADBValid
103.197.84.0/24APNICValid
103.197.85.0/24APNICValid
103.197.86.0/24APNICValid
103.197.87.0/24APNICValid
103.200.32.0/24APNIC, RADBValid
103.200.33.0/24APNIC, RADBValid
103.200.34.0/24APNIC, RADBValid
103.200.35.0/24APNIC, RADBValid
103.203.52.0/24APNIC, RADBValid
103.203.53.0/24APNIC, RADBValid
103.203.54.0/24APNIC, RADBValid
103.203.55.0/24APNIC, RADBValid
103.225.136.0/24APNIC, NTTCOM, RADBValid
103.225.137.0/24APNIC, NTTCOM, RADBValid
103.225.138.0/24APNIC, NTTCOM, RADBValid
103.225.139.0/24APNIC, NTTCOM, RADBValid
2001:470:658::/48ARINValid
2401:b80::/36APNICInvalid: maxLength
2401:b80:1000::/36APNIC, RADBValid
2401:b80:2000::/36APNIC, RADBValid
2401:b80:3000::/36APNIC, RADBValid
2401:b800::/32RADBNo ROA

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.