bgpreport

Network · data from 2026-11-12

AS219202 NEUROSIGNAL-AS NEUROSIGNAL LLC

Registry name: NEUROSIGNAL-AS NEUROSIGNAL LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219202, 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.131.212.0/24 Valid Other origin only 2 0%low visibility 2
193.233.255.0/24 Valid Other origin only 2 0%low visibility 2
45.9.118.0/24 Valid Other origin only 1 0%low visibility 1
45.128.78.0/24 Valid Other origin only 1 0%low visibility 1
103.91.147.0/24 Valid Other origin only 1 0%low visibility 1
113.30.154.0/24 Valid Other origin only 1 0%low visibility 1
156.242.88.0/24 Valid Other origin only 1 0%low visibility 1
37.235.250.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
154.80.172.0/24 Valid RIR databaseAFRINIC 1 0%low visibility 1

AS-SET

AS219202 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 28 are in fix.csv.

  • Route object: none7
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
Route object: none45.131.212.0/24Route objects for it name AS203273. Add a route object with origin AS219202 in the RIR database for the space.2 of 673
Route object: none193.233.255.0/24Route objects for it name AS29182. Add a route object with origin AS219202 in the RIR database for the space.2 of 673
Route object: none45.9.118.0/24Route objects for it name AS203273. Add a route object with origin AS219202 in the RIR database for the space.1 of 673
Route object: none45.128.78.0/24Route objects for it name AS203273. Add a route object with origin AS219202 in the RIR database for the space.1 of 673
Route object: none103.91.147.0/24Route objects for it name AS203273. Add a route object with origin AS219202 in the RIR database for the space.1 of 673
Route object: none113.30.154.0/24Route objects for it name AS203273. Add a route object with origin AS219202 in the RIR database for the space.1 of 673
Route object: none156.242.88.0/24Route objects for it name AS17561, AS152726, AS214483. Add a route object with origin AS219202 in the RIR database for the space.1 of 673

Route objects not announced

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

37.235.240.0/24RIPEValid
37.235.249.0/24RIPEValid
45.202.114.0/24AFRINICValid
45.203.191.0/24AFRINICValid
147.45.47.0/24RIPEInvalid: origin
154.80.129.0/24AFRINICValid
154.80.130.0/24AFRINICValid
154.80.131.0/24AFRINICValid
154.80.171.0/24AFRINICValid
154.81.190.0/24AFRINICValid
154.81.221.0/24AFRINICValid
154.83.149.0/24AFRINICValid
154.86.116.0/24AFRINICValid
154.86.118.0/24AFRINICValid
154.195.48.0/24AFRINICValid
154.195.51.0/24AFRINICValid
154.195.54.0/24AFRINICValid
154.216.131.0/24AFRINICValid
156.238.104.0/24AFRINICValid
178.130.132.0/24RIPEValid
193.223.104.0/24RIPEInvalid: origin

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.