Network · data from 2026-11-12
AS35004 Netgroup-Service
Registry name: NETGRUP Branch Enterprise "Netgroup-Service", UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35004, 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.
| 95.47.59.0/24 | Invalid: origin | Other origin only | 6 1%low visibility |
| 31.148.149.0/24 | Invalid: origin | Other origin only | 5 1%low visibility |
| 45.131.164.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.131.166.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.126.180.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 195.74.72.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.183.110.0/23 | No ROA | RIR databaseRIPE | 669 99% |
| 195.162.80.0/22 | No ROA | RIR databaseRIPE | 669 99% |
| 93.170.116.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 95.46.212.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 93.170.118.0/24 | Valid | RIR databaseRIPE | 140 21% |
AS-SET
PeeringDB's irr_as_set for AS35004: AS-NETGRUP. 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 (AS35004 isn't in the set, or no route object for AS35004 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 | AS35004 in it | Not covered |
|---|---|---|---|---|---|
| AS-NETGRUP | RIPE1 member set in no database: AS-INFOBYTE-IFIX | 41 | 11 | Yes | 2 |
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 16 are in fix.csv.
- ROA: origin2
- ROA: none6
- Route object: none2
- AS-SET: missing member1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 95.47.59.0/24 | ROAs covering it name AS44546, AS212463, not AS35004. If AS35004 should announce it, add a ROA for AS35004. |
| Route object: none | 95.47.59.0/24 | Route objects for it name AS212463. Add a route object with origin AS35004 in the RIR database for the space. |
| ROA: origin | 31.148.149.0/24 | ROAs covering it name AS44546, AS212463, not AS35004. If AS35004 should announce it, add a ROA for AS35004. |
| Route object: none | 31.148.149.0/24 | Route objects for it name AS212463. Add a route object with origin AS35004 in the RIR database for the space. |
| ROA: none | 45.131.164.0/24 | No ROA covers it. Add a ROA for AS35004, maxLength 24. |
| ROA: none | 45.131.166.0/24 | No ROA covers it. Add a ROA for AS35004, maxLength 24. |
| ROA: none | 194.126.180.0/22 | No ROA covers it. Add a ROA for AS35004, maxLength 22. |
| ROA: none | 195.74.72.0/24 | No ROA covers it. Add a ROA for AS35004, maxLength 24. |
| ROA: none | 185.183.110.0/23 | No ROA covers it. Add a ROA for AS35004, maxLength 23. |
| ROA: none | 195.162.80.0/22 | No ROA covers it. Add a ROA for AS35004, maxLength 22. |
| AS-SET: missing member | AS-NETGRUP | AS-NETGRUP (RIPE) lists AS-INFOBYTE-IFIX; no IRR database read has it. |
Route objects not announced
Route objects with origin AS35004 whose prefix no peer sees AS35004 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.170.116.0/24 | RIPE | Valid |
| 93.170.117.0/24 | RIPE | Valid |
| 93.170.119.0/24 | RIPE | Valid |
| 194.126.180.0/24 | RIPE | No ROA |
| 194.126.183.0/24 | RIPE | 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.