bgpreport

Network · data from 2026-11-12

AS205889 Giga Nineveh for internet services

Registry name: giganineveh Giga Nineveh for internet services Ltd, IQ · PeeringDB

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

Announced routes

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

185.185.172.0/24 Valid Other origin only 670 100% 67
185.135.68.0/24 Valid RIR databaseRIPE 672 100% 67
185.135.70.0/24 Valid RIR databaseRIPE 672 100% 67
185.185.173.0/24 Valid RIR databaseRIPE 672 100% 67
185.185.174.0/24 Valid RIR databaseRIPE 672 100% 67
185.203.53.0/24 Valid RIR databaseRIPE 672 100% 67
185.135.71.0/24 Valid RIR databaseRIPE 671 100% 67
185.135.69.0/24 Valid RIR databaseRIPE 670 100% 67
185.203.52.0/24 Valid RIR databaseRIPE 670 100% 67
185.203.54.0/24 Valid RIR databaseRIPE 670 100% 67
185.203.55.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

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

  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none185.185.172.0/24Route objects for it name AS203409. Add a route object with origin AS205889 in the RIR database for the space.670 of 673

Route objects not announced

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

185.185.175.0/24RIPEValid
185.203.52.0/22RIPENo ROA

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.