bgpreport

Network · data from 2026-11-12

AS219268 GeodemaGroup

Registry name: GeodemaGroup Geodema Group LLC, UA · PeeringDB

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

Announced routes

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

151.247.84.0/24 Invalid: origin None 70 10% 32
31.57.207.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.241.165.0/24 Invalid: origin None 2 0%low visibility 1
179.253.111.0/24 Valid None 670 100% 66
94.183.196.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.197.0/24 Valid RIR databaseRIPE 672 100% 66
177.3.200.0/24 Valid RIR databaseRIPE 672 100% 66
179.253.182.0/24 Valid RIR databaseRIPE 672 100% 66
201.58.133.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.195.0/24 Valid RIR databaseRIPE 671 100% 66
179.236.130.0/24 Valid RIR databaseRIPE 671 100% 66
201.8.82.0/24 Valid RIR databaseRIPE 671 100% 66
2a0f:6280:100a::/48 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS219268'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 12 are in fix.csv.

  • ROA: origin3
  • Route object: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin151.247.84.0/24ROAs covering it name AS834, not AS219268. If AS219268 should announce it, add a ROA for AS219268.70 of 673
Route object: none151.247.84.0/24No route object for it. Add a route object with origin AS219268 in the RIR database for the space.70 of 673
ROA: origin31.57.207.0/24ROAs covering it name AS834, not AS219268. If AS219268 should announce it, add a ROA for AS219268.2 of 673
Route object: none31.57.207.0/24Route objects for it name AS834. Add a route object with origin AS219268 in the RIR database for the space.2 of 673
ROA: origin151.241.165.0/24ROAs covering it name AS834, not AS219268. If AS219268 should announce it, add a ROA for AS219268.2 of 673
Route object: none151.241.165.0/24No route object for it. Add a route object with origin AS219268 in the RIR database for the space.2 of 673
Route object: none179.253.111.0/24No route object for it. Add a route object with origin AS219268 in the RIR database for the space.670 of 673

Route objects not announced

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

48.103.123.0/24RIPEValid
177.3.197.0/24RIPEValid
179.253.99.0/24RIPEValid
179.253.187.0/24RIPEValid
201.58.135.0/24RIPEValid

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.