Network · data from 2026-11-12
AS198077 Need
Registry name: NEEDTG-AS Need, L.L.C.-FZ, AE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198077, 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.
| 89.18.62.0/24 | Valid | Nonecovered by 89.18.60.0/22 | 673 100% |
| 89.18.60.0/24 | Valid | Nonecovered by 89.18.60.0/22 | 670 100% |
| 89.18.61.0/24 | Valid | Nonecovered by 89.18.60.0/22 | 2 0%low visibility |
| 85.208.113.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 109.106.15.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 145.79.176.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.255.247.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 192.142.8.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 192.142.23.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 195.252.179.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 169.40.34.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.254.168.0/24 | Valid | RIR databaseRADB, RIPE | 651 97% |
| 192.142.12.0/24 | Valid | RIR databaseAFRINIC | 624 93% |
AS-SET
PeeringDB's irr_as_set for AS198077: AS198077:AS-APRIL. 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 (AS198077 isn't in the set, or no route object for AS198077 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 | AS198077 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS198077:AS-APRIL | In no IRR database read today. | |||||
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 6 are in fix.csv.
- Route object: none3
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.18.62.0/24 | No route object for it. A route object for 89.18.60.0/22 with origin AS198077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198077 in the RIR database for the space. |
| Route object: none | 89.18.60.0/24 | No route object for it. A route object for 89.18.60.0/22 with origin AS198077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198077 in the RIR database for the space. |
| Route object: none | 89.18.61.0/24 | No route object for it. A route object for 89.18.60.0/22 with origin AS198077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198077 in the RIR database for the space. |
| AS-SET: not found | AS198077:AS-APRIL | PeeringDB names AS198077:AS-APRIL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS198077 whose prefix no peer sees AS198077 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.18.60.0/22 | RADB, RIPE | Valid |
| 89.18.63.0/24 | RIPE | 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.