bgpreport

Network · data from 2026-11-12

AS199654 OXIDE-GROUP-LIMITED Oxide Group Limited

Registry name: OXIDE-GROUP-LIMITED Oxide Group Limited, GB · not in PeeringDB

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

Announced routes

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

45.149.27.0/24 Invalid: origin Other origin only 32 5%low visibility 24
2a0f:b240:2f::/48 Valid Nonecovered by 2a0f:b240:20::/44 635 100% 69
2.56.164.0/24 Valid RIR databaseRIPE 671 100% 66
185.227.70.0/24 Valid RIR databaseRIPE 671 100% 66
195.58.58.0/24 Valid RIR databaseRIPE 671 100% 68
2a12:bec0:20a::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec0:20b::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec0:20c::/48 Valid RIR databaseRIPE 634 100% 70

AS-SET

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

  • ROA: origin1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin45.149.27.0/24ROAs covering it name AS206668, not AS199654. If AS199654 should announce it, add a ROA for AS199654.32 of 673
Route object: none45.149.27.0/24Route objects for it name AS206668. Add a route object with origin AS199654 in the RIR database for the space.32 of 673
Route object: none2a0f:b240:2f::/48No route object for it. A route object for 2a0f:b240:20::/44 with origin AS199654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199654 in the RIR database for the space.635 of 636

Route objects not announced

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

146.19.38.0/24RADB, RIPEValid
2a0f:b240:c::/48RIPEValid
2a0f:b240:20::/44RIPEValid

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.