AS33551
Sisters of Mercy Health System
AS33551 is Sisters of Mercy Health System (mercy.net). It announces 7,936 IPv4 addresses in 15 prefixes, and 0 IPv6 prefixes.
United States· ARIN· allocated 2005-01-19· business
7,936
IPv4 addresses announced
15
IPv4 prefixes
0
IPv6 prefixes
0.00%
of its routes RPKI-valid
7,936
of its IPv4 geolocated
1
country
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 States7,936 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- SISTERS-OF-MERCY-HEALTH-SYSTEM
- name
- Sisters of Mercy Health System
- org
- SMHS
- org name
- Sisters of Mercy Health System
- org address
- 3637 S. Geyer Rd., St. Louis, MO, 63127
- org city
- St. Louis
- org country
- US
- country
- US
- source
- arin
- created
- 2005-01-19
- updated
- 2026-06-06
- remarks
- Autonomous System for Sisters of Mercy Health System - / St. Louis, MO
- abuse name
- Nicolas Pagano
- abuse email
- nicolas.pagano@mercy.net
- abuse phone
- +1-314-364-3362
- abuse kind
- person
- abuse city
- Saint Louis
- abuse country
- US
- admin name
- Steve Saeger
- admin email
- steves@mercy.net
- admin phone
- +1-314-364-3240
- admin kind
- person
- admin city
- Sunset Hills
- admin country
- US
- tech
- PAGAN65-ARIN|SAEGE-ARIN
- tech name
- Nicolas Pagano
- tech email
- nicolas.pagano@mercy.net
- tech phone
- +1-314-364-3362
- tech kind
- person
- tech city
- Saint Louis
- 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.01%
- None here
- None here
- None here
- None here
- None here
- None here
- None here
- None here
- None here
- 0.04%
- None here
- 0.15%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 170.29.0.0/21 | United States | not found | 17 | 2026-10-02 |
| 170.29.0.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.9.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.10.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.11.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.12.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.30.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.32.0/21 | United States | not found | 17 | 2026-10-02 |
| 170.29.64.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.65.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.66.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.68.0/22 | United States | not found | 17 | 2026-10-02 |
| 170.29.72.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.73.0/24 | United States | not found | 17 | 2026-10-02 |
| 170.29.144.0/24 | United States | not found | 17 | 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.