bgpreport

Network · data from 2026-11-12

AS59597 4COM TECHNOLOGIES

Registry name: FOURCOM 4COM TECHNOLOGIES LIMITED, GB · PeeringDB

7IPv4 routes 85.7% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS59597, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59597, 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.
149.12.184.0/22 No ROA Other IRR onlyRADB, RIPE-NONAUTH 673 100% 67
5.179.72.0/21 Valid RIR databaseRIPE 673 100% 67
185.14.140.0/22 Valid RIR databaseRIPE 673 100% 67
193.176.4.0/24 Valid RIR databaseRIPE 672 100% 67
193.176.44.0/24 Valid RIR databaseRIPE 672 100% 67
193.176.62.0/24 Valid RIR databaseRIPE 672 100% 67
193.176.147.0/24 Valid RIR databaseRIPE 672 100% 67
2a01:9540::/32 Valid RIR databaseRIPE 636 100% 67
2a0f:90c0::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS59597: RIPE::AS-FOURCOM. 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 (AS59597 isn't in the set, or no route object for AS59597 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 objectsAS59597 in itNot covered
RIPE::AS-FOURCOM RIPE 119 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none149.12.184.0/22No ROA covers it. Add a ROA for AS59597, maxLength 22.673 of 673
Route object: RIR149.12.184.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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