bgpreport

Network · data from 2026-11-12

AS199746 SHRDSERV SharedServ Ltd

Registry name: SHRDSERV SharedServ Ltd, GB · not in PeeringDB

0IPv4 routes
8IPv6 routes 37.5% RPKI valid · 50.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
1No ROA 4 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS199746, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199746, 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.
2a05:dfc6:9500::/40 Invalid: origin None 1 0%low visibility 1
2a06:1283:891c::/48 Invalid: origin Other origin only 1 0%low visibility 1
2a14:7581:5020::/44 Invalid: origin None 0 0%low visibility 1
2a14:7581:5106::/48 Invalid: origin Other IRR onlyALTDB 64 10% 31
2a09:3f06:6767::/48 No ROA None 73 11% 29
2a06:1283:891a::/48 Valid Other IRR onlyRADB 2 0%low visibility 2
2a0b:4e07:2008::/46 Valid Other IRR onlyRADB 2 0%low visibility 2
2a06:1283:891b::/48 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS199746 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • ROA: origin4
  • ROA: none1
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2a05:dfc6:9500::/40ROAs covering it name AS133752, not AS199746. If AS199746 should announce it, add a ROA for AS199746.1 of 636
Route object: none2a05:dfc6:9500::/40No route object for it. Add a route object with origin AS199746 in the RIR database for the space.1 of 636
ROA: origin2a06:1283:891c::/48ROAs covering it name AS48700, AS213413, AS215147, AS219451, not AS199746. If AS199746 should announce it, add a ROA for AS199746.1 of 636
Route object: none2a06:1283:891c::/48Route objects for it name AS219451. Add a route object with origin AS199746 in the RIR database for the space.1 of 636
ROA: origin2a14:7581:5020::/44ROAs covering it name AS204464, not AS199746. If AS199746 should announce it, add a ROA for AS199746.0 of 636
Route object: none2a14:7581:5020::/44No route object for it. Add a route object with origin AS199746 in the RIR database for the space.0 of 636
ROA: origin2a14:7581:5106::/48ROAs covering it name AS204464, not AS199746. If AS199746 should announce it, add a ROA for AS199746.64 of 636
Route object: RIR2a14:7581:5106::/48Route object only in ALTDB. Add it in the RIR database for the space.64 of 636
ROA: none2a09:3f06:6767::/48No ROA covers it. Add a ROA for AS199746, maxLength 48.73 of 636
Route object: none2a09:3f06:6767::/48No route object for it. Add a route object with origin AS199746 in the RIR database for the space.73 of 636
Route object: RIR2a06:1283:891a::/48Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2a0b:4e07:2008::/46Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

2a05:dfc6::/36ALTDBInvalid: origin
2a06:1283:8908::/48RADB, RIPEValid
2a06:1283:8912::/48RIPEValid
2a0d:d940:2017::/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.