AS398493
System In Place
AS398493 is System In Place (systeminplace.net). It announces 6,400 IPv4 addresses in 17 prefixes, and 27 IPv6 prefixes.
United States· ARIN· allocated 2020-07-01· hosting
6,400
IPv4 addresses announced
17
IPv4 prefixes
27
IPv6 prefixes
100.00%
of its routes RPKI-valid
6,400
of its IPv4 geolocated
4
countries
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- United States5,000 · 78.13%
- United Kingdom1,304 · 20.38%
- Australia64 · 1.00%
- India32 · 0.50%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- SYSTEMINPLACE
- name
- System In Place
- org
- MS-1790
- org name
- System In Place
- org address
- 2108 N ST STE N, Sacramento, CA, 95816
- org city
- Sacramento
- org country
- US
- country
- US
- source
- arin
- created
- 2020-07-01
- updated
- 2020-07-01
- abuse name
- Michael Smith
- abuse email
- abuse@systeminplace.net
- abuse phone
- +1-443-267-8465
- abuse kind
- person
- abuse city
- Sacramento
- abuse country
- US
- admin name
- Michael Smith
- admin email
- abuse@systeminplace.net
- admin phone
- +1-443-267-8465
- admin kind
- person
- admin city
- Sacramento
- admin country
- US
- tech name
- Michael Smith
- tech email
- abuse@systeminplace.net
- tech phone
- +1-443-267-8465
- tech kind
- person
- tech city
- Sacramento
- tech country
- US
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- 0.03%
- dataimpulse, hydraproxy, geonode0.22%
- floppydata0.13%
- None here
- None here
- None here
- Hosting IP4,86476.00%
- None here
- None here
- None here
- SSH IP5568.69%
- SMTP IP891.39%
- 1.52%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 23.161.112.0/24 | United States | valid | 18 | 2026-10-02 |
| 23.185.72.0/24 | United States | valid | 18 | 2026-10-02 |
| 69.176.84.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 74.117.196.0/22 | United States | valid | 18 | 2026-10-02 |
| 104.250.236.0/22 | United States | valid | 18 | 2026-10-02 |
| 107.149.33.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 108.186.51.0/24 | United States | valid | 18 | 2026-10-02 |
| 108.186.146.0/24 | United States | valid | 18 | 2026-10-02 |
| 144.225.246.0/23 | United Kingdom | valid | 18 | 2026-10-02 |
| 144.225.246.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 144.225.247.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 151.244.214.0/24 | United States | valid | 18 | 2026-10-02 |
| 166.88.232.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 169.128.158.0/24 | United States | valid | 18 | 2026-10-02 |
| 169.128.159.0/24 | United States | valid | 18 | 2026-10-02 |
| 170.39.20.0/24 | United States | valid | 18 | 2026-10-02 |
| 204.197.160.0/22 | United States | valid | 18 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2602:fd37::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:1::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:2::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:4::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:100::/40 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:200::/40 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:300::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:301::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:302::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:303::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:304::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:305::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:306::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:307::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:308::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:309::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:30a::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:310::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:311::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:312::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:313::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:314::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:315::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:316::/48 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:400::/40 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:500::/40 | United States | valid | 20 | 2026-10-02 |
| 2602:fd37:fff::/48 | United States | valid | 20 | 2026-10-02 |
00 · Evaluate
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.
01 · License
Then license what you use.
Standard, for detection and decisions inside your own product and operations.
Redistribution, when the data ships onward inside what you sell — priced by scope, not by seat.
Annual terms, a named contact, and flexible payment terms — monthly, quarterly or yearly.