bgpreport

Network · data from 2026-11-12

AS31490 NetIX-MGMT-AS NetIX Communications JSC

Registry name: NetIX-MGMT-AS NetIX Communications JSC, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31490, 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.
2a00:1728:21:100::/56 Invalid: origin None 3 0%low visibility 4
2a00:1728:20:100::/56 Valid Nonecovered by 2a00:1728:20::/48 11 2%low visibility 12
85.217.188.0/24 Valid RIR databaseRIPE 673 100% 66
93.123.23.0/24 Valid RIR databaseRIPE 673 100% 66
94.156.178.0/24 Valid RIR databaseRIPE 673 100% 66
94.156.188.0/24 Valid RIR databaseRIPE 673 100% 66
94.156.233.0/24 Valid RIR databaseRIPE 673 100% 66
87.121.121.0/24 Valid RIR databaseRIPE 671 100% 67
185.219.124.0/24 Valid RIR databaseRIPE 671 100% 66
2a00:1728:20::/48 Valid RIR databaseRIPE 636 100% 67
2a14:44c0::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

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

  • ROA: origin1
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a00:1728:21:100::/56ROAs covering it name AS34224, not AS31490. If AS31490 should announce it, add a ROA for AS31490.3 of 636
Route object: none2a00:1728:21:100::/56No route object for it. Add a route object with origin AS31490 in the RIR database for the space.3 of 636
Route object: none2a00:1728:20:100::/56No route object for it. A route object for 2a00:1728:20::/48 with origin AS31490 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS31490 in the RIR database for the space.11 of 636

Route objects not announced

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

2a00:1728:33::/48RIPEValid
2a14:44c0:4::/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.