bgpreport

Network · data from 2026-11-12

AS134595 Velocity Internet

Registry name: VELOCITYINTERNET-AS-AP - Velocity Internet, BD · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
17IPv6 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
0Route objects not announced registered with origin AS134595, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134595, 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.121.12.0/24 Valid RIR databaseAPNIC 673 100% 67
103.121.14.0/24 Valid RIR databaseAPNIC 673 100% 67
103.121.15.0/24 Valid RIR databaseAPNIC 673 100% 67
103.121.13.0/24 Valid RIR databaseAPNIC 672 100% 67
103.170.231.0/24 Valid RIR databaseAPNIC 672 100% 67
2403:6240::/32 Valid RIR databaseAPNIC 635 100% 70
2403:6240::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:1000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:2000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:3000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:4000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:5000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:6000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:7000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:8000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:9000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:a000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:b000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:c000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:d000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:e000::/36 Valid RIR databaseAPNIC 635 100% 70
2403:6240:f000::/36 Valid RIR databaseAPNIC 635 100% 70

AS-SET

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

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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