bgpreport

Network · data from 2026-11-12

AS215311 REGXA-CLOUD

Registry name: REGXA-CLOUD Regxa Company for Information Technology Ltd, IQ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215311, 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.
206.206.76.0/22 Valid Other IRR onlyRADB 663 99% 67
83.147.18.0/24 Valid RIR databaseRADB, RIPE 667 99% 66
83.147.19.0/24 Valid RIR databaseRADB, RIPE 667 99% 66
145.223.68.0/22 Valid RIR databaseRADB, RIPE 667 99% 66
146.103.40.0/22 Valid RIR databaseRADB, RIPE 667 99% 66
150.251.112.0/22 Valid RIR databaseRIPE 667 99% 66
193.56.135.0/24 Valid RIR databaseRIPE 667 99% 66
194.150.166.0/24 Valid RIR databaseRIPE 667 99% 66
209.200.246.0/23 Valid RIR databaseARIN, RADB 667 99% 66
2a14:4200::/29 Valid RIR databaseRADB, RIPE 630 99% 67

AS-SET

PeeringDB's irr_as_set for AS215311: AS-REGXACLOUD-TRANSIT. 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 (AS215311 isn't in the set, or no route object for AS215311 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 objectsAS215311 in itNot covered
AS-REGXACLOUD-TRANSIT In no IRR database read today.

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

  • Route object: RIR1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR206.206.76.0/22Route object only in RADB. Add it in the RIR database for the space.663 of 673
AS-SET: not foundAS-REGXACLOUD-TRANSITPeeringDB names AS-REGXACLOUD-TRANSIT; no IRR database read has it.

Route objects not announced

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