bgpreport

Network · data from 2026-11-12

AS207609 Sepehr Ahmadi

Registry name: GOCOD-207609 - GoCodeIT Inc, CA · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS207609, seen from no peer

Announced routes

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

170.39.231.0/24 No ROA None 652 97% 68
2602:fd50:1::/48 No ROA RIR databaseARIN 634 100% 69
2602:fd50:200::/40 No ROA RIR databaseARIN 634 100% 69
2602:fd50:f20::/44 No ROA RIR databaseARIN 634 100% 69
130.12.160.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS207609: AS-GCT-V. 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 (AS207609 isn't in the set, or no route object for AS207609 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 objectsAS207609 in itNot covered
AS-GCT-V RIPE 2141 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: none4
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none170.39.231.0/24No ROA covers it. Add a ROA for AS207609, maxLength 24.652 of 673
Route object: none170.39.231.0/24No route object for it. Add a route object with origin AS207609 in the RIR database for the space.652 of 673
ROA: none2602:fd50:1::/48No ROA covers it. Add a ROA for AS207609, maxLength 48.634 of 636
ROA: none2602:fd50:200::/40No ROA covers it. Add a ROA for AS207609, maxLength 40.634 of 636
ROA: none2602:fd50:f20::/44No ROA covers it. Add a ROA for AS207609, maxLength 44.634 of 636

Route objects not announced

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

2602:fd50:10::/44ARINNo ROA
2602:fd50:10::/48ARINNo 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.