bgpreport

Network · data from 2026-11-12

AS206033 Repox Labs

Registry name: REPOXLABS Repox Labs Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206033, 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.
104.233.185.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.227.72.0/24 Valid RIR databaseRIPE 670 100% 67
2a13:9500:6b::/48 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS206033: AS206033:AS-REPOXLABS. 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 (AS206033 isn't in the set, or no route object for AS206033 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 objectsAS206033 in itNot covered
AS206033:AS-REPOXLABS RIPElists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7147620,801 Yes 1

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 7 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
ROA: origin104.233.185.0/24ROAs covering it name AS834, not AS206033. If AS206033 should announce it, add a ROA for AS206033.2 of 673
Route object: none104.233.185.0/24Route objects for it name AS834. Add a route object with origin AS206033 in the RIR database for the space.2 of 673
AS-SET: missing memberAS206033:AS-REPOXLABSAS206033:AS-REPOXLABS (RIPE) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS206033:AS-REPOXLABSAS206033:AS-REPOXLABS (RIPE) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS206033:AS-REPOXLABSAS206033:AS-REPOXLABS (RIPE) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS206033:AS-REPOXLABSAS206033:AS-REPOXLABS (RIPE) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS206033:AS-REPOXLABSAS206033:AS-REPOXLABS (RIPE) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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