Network · data from 2026-11-12
AS3507 IPSWAT TEAM
Registry name: IPSWAT TEAM - IPSwat LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3507, 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.
| 136.175.56.0/24 | No ROA | Other origin onlycovered by 136.175.56.0/22 | 669 99% |
| 136.175.57.0/24 | No ROA | Other origin onlycovered by 136.175.56.0/22 | 669 99% |
| 23.188.208.0/24 | No ROA | RIR databaseARIN | 627 93% |
| 23.128.48.0/24 | Valid | RIR databaseARIN | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS3507: ALTDB::AS-AS3507. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS3507 isn't in the set, or no route object for AS3507 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS3507 in it | Not covered |
|---|---|---|---|---|---|
| ALTDB::AS-AS3507 | ALTDB | 23 | 1 | Yes | 0 |
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 9 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 136.175.56.0/24 | No ROA covers it. Add a ROA for AS3507, maxLength 24. |
| Route object: none | 136.175.56.0/24 | Route objects for it name AS7029, AS399989. A route object for 136.175.56.0/22 with origin AS3507 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3507 in the RIR database for the space. |
| ROA: none | 136.175.57.0/24 | No ROA covers it. Add a ROA for AS3507, maxLength 24. |
| Route object: none | 136.175.57.0/24 | Route objects for it name AS7029, AS399989. A route object for 136.175.56.0/22 with origin AS3507 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3507 in the RIR database for the space. |
| ROA: none | 23.188.208.0/24 | No ROA covers it. Add a ROA for AS3507, maxLength 24. |
Route objects not announced
Route objects with origin AS3507 whose prefix no peer sees AS3507 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.190.120.0/24 | ARIN | No ROA |
| 136.175.56.0/22 | ARIN | No ROA |
| 2001:470:440::/48 | ARIN | Valid |
| 2607:d740::/32 | ARIN | No ROA |
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.