Network · data from 2026-11-12
AS263570 AS263570 - JF PROVEDOR DE INTERNET LTDA
Registry name: AS263570 - JF PROVEDOR DE INTERNET LTDA, BR · not in PeeringDB
15IPv4 routes
100.0% RPKI valid · 60.0% with a route object
5IPv6 routes
100.0% RPKI valid · 20.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
10 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS263570, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS263570, 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.
| 186.249.248.0/22 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 186.249.248.0/23 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 186.249.250.0/23 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 186.249.252.0/22 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 186.249.252.0/23 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 186.249.254.0/23 | Valid | Nonecovered by 186.249.248.0/21 | 672 100% |
| 2804:f34::/34 | Valid | Nonecovered by 2804:f34::/32 | 635 100% |
| 2804:f34:4000::/34 | Valid | Nonecovered by 2804:f34::/32 | 635 100% |
| 2804:f34:8000::/34 | Valid | Nonecovered by 2804:f34::/32 | 635 100% |
| 2804:f34:c000::/34 | Valid | Nonecovered by 2804:f34::/32 | 635 100% |
| 186.249.248.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.248.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.250.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.252.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.253.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.254.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.255.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 186.249.249.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 186.249.251.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2804:f34::/32 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS263570 isn't in PeeringDB, where networks name their AS-SET.
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 20 are in fix.csv.
- Route object: none10
- Route object: RIR10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.249.248.0/22 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 186.249.248.0/23 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 186.249.250.0/23 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 186.249.252.0/22 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 186.249.252.0/23 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 186.249.254.0/23 | No route object for it. A route object for 186.249.248.0/21 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 2804:f34::/34 | No route object for it. A route object for 2804:f34::/32 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 2804:f34:4000::/34 | No route object for it. A route object for 2804:f34::/32 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 2804:f34:8000::/34 | No route object for it. A route object for 2804:f34::/32 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: none | 2804:f34:c000::/34 | No route object for it. A route object for 2804:f34::/32 with origin AS263570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263570 in the RIR database for the space. |
| Route object: RIR | 186.249.248.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.252.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.253.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.249.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:f34::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS263570 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.