bgpreport

Network · data from 2026-11-12

AS48866 NETCRACKER-EMEA-AS Netcracker Technology EMEA Limited

Registry name: NETCRACKER-EMEA-AS Netcracker Technology EMEA Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48866, 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.
109.245.246.152/29 Invalid: origin None 2 0%low visibility 2
154.61.134.0/24 No ROA None 673 100% 67
192.231.26.0/24 Valid RIR databaseRIPE 673 100% 67
193.218.186.0/24 Valid RIR databaseRIPE 673 100% 67
195.191.41.0/24 Valid RIR databaseRIPE 673 100% 67
195.211.250.0/24 Valid RIR databaseRIPE 673 100% 67
91.223.178.0/24 Valid RIR databaseRIPE 671 100% 68
195.191.40.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin109.245.246.152/29ROAs covering it name AS15958, not AS48866. If AS48866 should announce it, add a ROA for AS48866.2 of 673
Route object: none109.245.246.152/29No route object for it. Add a route object with origin AS48866 in the RIR database for the space.2 of 673
ROA: none154.61.134.0/24No ROA covers it. Add a ROA for AS48866, maxLength 24.673 of 673
Route object: none154.61.134.0/24No route object for it. Add a route object with origin AS48866 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS48866 is announced.

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.