Network · data from 2026-11-12
AS203939 Mosaic Data Services, Inc.
Registry name: MOSAIC - Mosaic Data Services, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203939, 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.
| 23.136.116.0/24 | Valid | RIR databaseARIN | 671 100% |
| 185.125.184.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.204.14.0/23 | Valid | RIR databaseARIN | 671 100% |
| 2602:f6a7::/36 | Valid | RIR databaseARIN | 635 100% |
| 2a06:bc40::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS203939: ARIN::AS203939:AS-MOSAIC. 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 (AS203939 isn't in the set, or no route object for AS203939 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 | AS203939 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS203939:AS-MOSAIC | ARIN1 member set in no database: AS61961:AS-NELLICUS | 6 | 5 | 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 1 are in fix.csv.
- AS-SET: missing member1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | ARIN::AS203939:AS-MOSAIC | AS203939:AS-MOSAIC (ARIN) lists AS61961:AS-NELLICUS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS203939 is announced.
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.