Network · data from 2026-11-12
AS263991 WFNET INTERNET
Registry name: AS263991 - WFNET INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263991, 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.
| 2804:28fc::/33 | Valid | Nonecovered by 2804:28fc::/32 | 632 99% |
| 143.0.28.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 170.245.16.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 170.245.19.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 2804:28fc::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:28fc:8000::/33 | Valid | Other IRR onlyRADB | 632 99% |
| 143.0.28.0/23 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 143.0.30.0/23 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 170.245.16.0/23 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 170.245.18.0/23 | Valid | Other IRR onlyTC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS263991: AS263991:AS-GLOBAL. 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 (AS263991 isn't in the set, or no route object for AS263991 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 | AS263991 in it | Not covered |
|---|---|---|---|---|---|
| AS263991:AS-GLOBAL | TC | 6 | 1 | No | 10 |
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 18 are in fix.csv.
- Route object: none1
- Route object: RIR9
- AS-SET: own ASN1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:28fc::/33 | No route object for it. A route object for 2804:28fc::/32 with origin AS263991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263991 in the RIR database for the space. |
| Route object: RIR | 143.0.28.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.16.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.19.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:28fc::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:28fc:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.0.28.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.0.30.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.16.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.18.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS263991:AS-GLOBAL | AS263991 isn't in AS263991:AS-GLOBAL (TC) once expanded. Add AS263991 to it. |
Route objects not announced
Route objects with origin AS263991 whose prefix no peer sees AS263991 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.0.28.0/24 | TC | Valid |
| 143.0.29.0/24 | TC | Valid |
| 143.0.30.0/24 | TC | Valid |
| 143.0.31.0/24 | TC | Valid |
| 170.245.16.0/24 | TC | Valid |
| 170.245.17.0/24 | TC | Valid |
| 170.245.18.0/24 | TC | 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.