bgpreport

Network · data from 2026-11-12

AS211545 Prodigy LTD

Registry name: Prodigy-AS Prodigy LTD, BG · PeeringDB

6IPv4 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
0Route objects not announced registered with origin AS211545, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211545, 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.
82.119.71.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.204.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.205.0/24 Valid RIR databaseRIPE 673 100% 66
176.67.236.0/24 Valid RIR databaseRIPE 673 100% 66
176.67.237.0/24 Valid RIR databaseRIPE 673 100% 66
176.67.239.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

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