bgpreport

Network · data from 2026-11-12

AS329181 Bluedog Technology

Registry name: Bluedog Technology - Bluedog Technology, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329181, 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.
2c0f:6500::/33 Valid Nonecovered by 2c0f:6500::/32 31 5%low visibility 15
102.217.136.0/22 Valid RIR databaseAFRINIC 670 100% 68
102.218.220.0/22 Valid RIR databaseAFRINIC 670 100% 68
102.219.12.0/22 Valid RIR databaseAFRINIC 670 100% 68
2c0f:1900::/32 Valid RIR databaseAFRINIC 634 100% 69
2c0f:6500::/32 Valid RIR databaseAFRINIC 634 100% 69
102.217.136.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.217.137.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.217.138.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.217.139.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.218.220.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.218.221.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.218.222.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.218.223.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.219.12.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.219.13.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.219.14.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
102.219.15.0/24 Valid RIR databaseAFRINIC 47 7%low visibility 20
2c0f:1900::/33 Valid RIR databaseAFRINIC 31 5%low visibility 15
2c0f:1900:8000::/33 Valid RIR databaseAFRINIC 31 5%low visibility 15
2c0f:6500:8000::/33 Valid RIR databaseAFRINIC 31 5%low visibility 15

AS-SET

PeeringDB's irr_as_set for AS329181: AS-OPNAXS. 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 (AS329181 isn't in the set, or no route object for AS329181 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 objectsAS329181 in itNot covered
AS-OPNAXS AFRINIC 1120 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2c0f:6500::/33No route object for it. A route object for 2c0f:6500::/32 with origin AS329181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329181 in the RIR database for the space.31 of 636

Route objects not announced

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