Network · data from 2026-11-12
AS62537 Sauce Labs Inc
Registry name: SLINC - Sauce Labs Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62537, 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.
| 66.85.48.0/22 | Valid | Nonecovered by 66.85.48.0/21 | 671 100% |
| 66.85.52.0/23 | Valid | Nonecovered by 66.85.48.0/21 | 671 100% |
| 66.85.48.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 66.85.54.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 151.158.35.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 185.94.26.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 185.94.24.0/23 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 185.94.24.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 185.94.26.0/23 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS62537: AS-SLINC. 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 (AS62537 isn't in the set, or no route object for AS62537 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 | AS62537 in it | Not covered |
|---|---|---|---|---|---|
| AS-SLINC | RADB | 1 | 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 14 are in fix.csv.
- Route object: none2
- Route object: RIR2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.85.48.0/22 | No route object for it. A route object for 66.85.48.0/21 with origin AS62537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62537 in the RIR database for the space. |
| Route object: none | 66.85.52.0/23 | No route object for it. A route object for 66.85.48.0/21 with origin AS62537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62537 in the RIR database for the space. |
| Route object: RIR | 66.85.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 66.85.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62537 whose prefix no peer sees AS62537 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.85.48.0/21 | RADB | Valid |
| 66.85.52.0/24 | RADB | Valid |
| 162.222.72.0/21 | RADB | Valid |
| 162.222.78.0/24 | RADB | Valid |
| 162.222.79.0/24 | RADB | Valid |
| 185.94.24.0/22 | RADB, RIPE | Valid |
| 185.94.25.0/24 | RADB, RIPE | Valid |
| 185.94.27.0/24 | RADB, RIPE | Valid |
| 2001:470:9::/48 | ARIN | Valid |
| 2001:470:40d::/48 | ARIN | Valid |
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.