Network · data from 2026-11-12
AS149476 FogNet APAC
Registry name: IFOGGMBH-AS-AP - iFog GmbH, CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149476, 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.
| 2400:54a0:2040::/44 | Valid | Nonecovered by 2400:54a0::/32 | 632 99% |
| 2a10:a507:b00b::/48 | Valid | Other origin only | 64 10% |
| 2400:54a0::/48 | Valid | RIR databaseAPNIC | 633 100% |
| 2400:54a0:1004::/48 | Valid | RIR databaseAPNIC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS149476: AS-IFOG-APAC. 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 (AS149476 isn't in the set, or no route object for AS149476 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 | AS149476 in it | Not covered |
|---|---|---|---|---|---|
| AS-IFOG-APAC | RIPElists itself further down | 82 | 14 | Yes | 1 |
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 10 are in fix.csv.
- Route object: none2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2400:54a0:2040::/44 | No route object for it. A route object for 2400:54a0::/32 with origin AS149476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149476 in the RIR database for the space. |
| Route object: none | 2a10:a507:b00b::/48 | Route objects for it name AS209022. Add a route object with origin AS149476 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS149476 whose prefix no peer sees AS149476 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.180.192.0/23 | APNIC | No ROA |
| 103.180.192.0/24 | APNIC | Invalid: origin |
| 103.180.193.0/24 | APNIC | Invalid: origin |
| 2400:54a0::/32 | APNIC | No ROA |
| 2400:54a0:1030::/48 | APNIC | Valid |
| 2a0c:9a40:9c00::/40 | RIPE | Valid |
| 2a0c:9a40:9c20::/44 | RIPE | Valid |
| 2a10:ccc3:ccc0::/46 | 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.