Skip to main content

AS4927

IMPU

Aseva LLC

Registry

Authoritative registration data

AS number
4927
Name
IMPU
Organisation
Aseva LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

2

Total announced

15

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS4927
207.154.64.0/18 IPv4 /18 not checked
207.71.192.0/18 IPv4 /18 not checked
205.254.224.0/19 IPv4 /19 not checked
64.4.128.0/19 IPv4 /19 not checked
64.29.224.0/20 IPv4 /20 not checked
64.68.128.0/21 IPv4 /21 not checked
64.68.136.0/21 IPv4 /21 not checked
208.47.64.0/22 IPv4 /22 not checked
199.201.128.0/24 IPv4 /24 not checked
207.154.67.0/24 IPv4 /24 not checked
207.154.68.0/24 IPv4 /24 not checked
64.4.132.0/24 IPv4 /24 not checked
64.68.142.0/24 IPv4 /24 not checked
2001:19f8::/32 IPv6 /32 not checked
2001:19f8:8000::/36 IPv6 /36 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS4927 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS4927 in AS paths

Observed upstreams
Families
AS6939 1,383 7,488
v4 v6
AS3356 391 1,117
v4 v6
AS13335 289 932
v4
AS174 172 495
v4 v6
AS137409 10 27
v4 v6
AS37468 4 10
v4
AS6057 6 8
v6
AS7195 1 1
v4
AS7575 1 1
v4

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS4927 in AS paths

Observed downstreams
Families
AS10596 341 3,776
v4 v6
AS26402 487 710
v4 v6
AS12210 277 380
v4
AS30412 277 380
v4
AS3356 3 13
v4
AS6939 1 2
v4

No rows match “”.

Showing of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 7 105
v4 v6
AS19151 7 54
v4 v6
AS49544 5 50
v4 v6
AS1828 7 27
v4 v6
AS36236 5 25
v4 v6
AS17639 5 21
v4
AS51185 2 10
v4
AS45489 3 4
v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.