Country
—
ASN LANDING PAGE
GSHAPIRO-AS Gregory Shapiro
Last updated · Jul 20, 2026
Country
—
Total prefixes
38
IPv4 prefixes
2
IPv6 prefixes
36
GSHAPIRO-AS Gregory Shapiro currently reports 38 prefixes and 35 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
GSHAPIRO-AS Gregory Shapiro is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS6939
AS6939
—
AS142064
AS142064
—
AS52025
AS52025
—
AS219331
AS219331
—
AS37988
AS37988
—
AS61138
AS61138
—
AS210475
AS210475
—
AS44324
AS44324
—
AS214675
AS214675
—
AS214955
AS214955
—
AS34927
AS34927
—
AS41051
AS41051
—
AS214757
AS214757
—
AS210464
AS210464
—
AS400587
AS400587
—
AS47272
AS47272
—
AS58057
AS58057
—
AS209533
AS209533
—
AS211509
AS211509
—
AS924
AS924
—
AS36236
AS36236
—
AS49134
AS49134
—
AS50869
AS50869
—
AS206271
AS206271
—
AS212508
AS212508
—
AS7721
AS7721
—
AS35708
AS35708
—
AS39351
AS39351
—
AS47498
AS47498
—
AS60326
AS60326
—
AS205794
AS205794
—
AS209022
AS209022
—
AS209823
AS209823
—
AS215628
AS215628
—
| Prefix | Name | Country |
|---|---|---|
| 198.180.151.0/24 | AS199518 | — |
| 2602:f9a2:55::/48 | AS199518 | — |
| 2602:faa5:f01::/48 | AS199518 | — |
| 2602:faa5:f04::/48 | AS199518 | — |
| 2a07:54c1:4242::/48 | AS199518 | — |
| 2a0a:280:2304::/48 | AS199518 | — |
| 2a0a:280:2309::/48 | AS199518 | — |
| 2a0a:280:2310::/48 | AS199518 | — |
| 2a0a:280:2311::/48 | AS199518 | — |
| 2a0a:280:2333::/48 | AS199518 | — |
| 2a0a:280:2345::/48 | AS199518 | — |
| 2a0a:280:2347::/48 | AS199518 | — |
| 2a0a:280:2352::/48 | AS199518 | — |
| 2a0a:280:2357::/48 | AS199518 | — |
| 2a0a:280:2371::/48 | AS199518 | — |
| 2a0a:280:2377::/48 | AS199518 | — |
| 2a0a:280:2381::/48 | AS199518 | — |
| 2a0a:280:2383::/48 | AS199518 | — |
| 2a0a:280:2388::/48 | AS199518 | — |
| 2a0a:280:2389::/48 | AS199518 | — |
| 2a0a:280:2393::/48 | AS199518 | — |
| 2a0a:6040:ba11::/48 | AS199518 | — |
| 2a0a:6040:ba15::/48 | AS199518 | — |
| 2a0a:6040:ba17::/48 | AS199518 | — |
| 2a0a:6040:ba1d::/48 | AS199518 | — |
| 2a0a:6040:ba1e::/48 | AS199518 | — |
| 2a0a:6040:ba55::/48 | AS199518 | — |
| 2a0a:6040:ba57::/48 | AS199518 | — |
| 2a0a:6040:ba5e::/48 | AS199518 | — |
| 2a0a:6040:ba75::/48 | AS199518 | — |
| 2a0a:6040:ba7e::/48 | AS199518 | — |
| 2a0a:6040:baa1::/48 | AS199518 | — |
| 2a0a:6040:baba::/48 | AS199518 | — |
| 2a0a:6040:bade::/48 | AS199518 | — |
| 2a0a:6040:baf7::/48 | AS199518 | — |
| 2a0a:6040:baff::/48 | AS199518 | — |
| 2a0f:b241:85::/48 | AS199518 | — |
| 44.31.140.0/24 | AS199518 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS199518 is an autonomous system number. The current source associates it with GSHAPIRO-AS Gregory Shapiro and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS199518. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS199518, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.