bgpreport

Network · data from 2026-11-12

AS9179 OfficeNet

Registry name: OFFICENET OfficeNet Systems Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9179, 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.
193.26.210.0/24 No ROA Nonecovered by 193.26.210.0/23 671 100% 67
185.11.204.0/22 No ROA Other origin only 651 97% 67

AS-SET

AS9179's PeeringDB record names no AS-SET.

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none193.26.210.0/24No ROA covers it. Add a ROA for AS9179, maxLength 24.671 of 673
Route object: none193.26.210.0/24No route object for it. A route object for 193.26.210.0/23 with origin AS9179 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9179 in the RIR database for the space.671 of 673
ROA: none185.11.204.0/22No ROA covers it. Add a ROA for AS9179, maxLength 22.651 of 673
Route object: none185.11.204.0/22Route objects for it name AS30909. Add a route object with origin AS9179 in the RIR database for the space.651 of 673

Route objects not announced

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

192.88.83.0/24RADBNo ROA
193.26.210.0/23RIPENo ROA
193.26.212.0/23RIPENo ROA
193.195.141.0/24RADBNo ROA
2a01:2c0:23db::/48RADBNo 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.