bgpreport

Network · data from 2026-11-12

AS49832 Qbic Communications

Registry name: AS-QBIC QBIC COMMUNICATIONS FZCO, AE · PeeringDB

1IPv4 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
14Route objects not announced registered with origin AS49832, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49832, 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.

167.160.20.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS49832: RIPE::AS-QBICOM. 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 (AS49832 isn't in the set, or no route object for AS49832 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 objectsAS49832 in itNot covered
RIPE::AS-QBICOM RIPElists itself further down10 member sets in no database: AS-207057, AS-ABRARVAN, AS-ALSARDFIBER, AS-DIJLAISPLTD, AS-HAYAT … 1,24662115,996 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 24 are in fix.csv.

  • AS-SET: missing member10
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-207057; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-ABRARVAN; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-ALSARDFIBER; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-DIJLAISPLTD; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-HAYAT; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-IRNA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-MORVA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-PCC; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS-SEFROYEK; no IRR database read has it.
AS-SET: missing memberRIPE::AS-QBICOMAS-QBICOM (RIPE) lists AS131284:AS-ETA; no IRR database read has it.

Route objects not announced

Route objects with origin AS49832 whose prefix no peer sees AS49832 announce. Many are kept on purpose (backup routes, space announced only in some places).

91.132.164.0/22RIPENo ROA
91.132.164.0/23RIPEInvalid: origin
91.132.164.0/24RIPEInvalid: origin
91.132.165.0/24RIPEInvalid: origin
91.132.166.0/23RIPEInvalid: origin
91.132.166.0/24RIPEInvalid: origin
91.132.167.0/24RIPEInvalid: origin
185.16.24.0/24RIPEValid
185.88.11.0/24RIPEValid
2a06:1ec0::/29RIPEValid
2a06:1ec0::/32RIPEValid
2a06:1ec0::/48RIPEValid
2a06:1ec7:100:100::/56RIPEValid
2a06:1ec7:2000::/48RIPEValid

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.