bgpreport

Network · data from 2026-11-12

AS198657 Kai Gohegan

Registry name: GOHEGAN-NET Kai Gohegan, GB · PeeringDB

0IPv4 routes
2IPv6 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
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS198657, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198657, 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.
2a06:9801:287::/48 Valid RIR databaseRIPE 4 1%low visibility 4
2a0b:4e07:2800::/40 Valid RIR databaseRIPE 4 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS198657: RIPE::AS-GOHEGAN-NET. 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 (AS198657 isn't in the set, or no route object for AS198657 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 objectsAS198657 in itNot covered
RIPE::AS-GOHEGAN-NET 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 3 are in fix.csv.

  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: not foundRIPE::AS-GOHEGAN-NETPeeringDB names RIPE::AS-GOHEGAN-NET; no IRR database read has it.

Route objects not announced

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

91.237.236.0/22RIPEValid
2001:67c:2b7c::/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.