bgpreport

Network · data from 2026-11-12

AS271567 AS271567 - JONATAN S COSTA COMUNICACAO MULTIMIDIA ME

Registry name: AS271567 - JONATAN S COSTA COMUNICACAO MULTIMIDIA ME, BR · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS271567, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271567, 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:7d88:8000::/34 Valid Nonecovered by 2804:7d88:8000::/33 627 99% 67
2804:7d88::/33 Valid Nonecovered by 2804:7d88::/32 626 98% 67
2804:7d88::/34 Valid Nonecovered by 2804:7d88::/32 626 98% 67
181.232.248.0/23 Valid Other IRR onlyRADB 665 99% 67
181.232.249.0/24 Valid Other IRR onlyRADB 665 99% 67
181.232.248.0/24 Valid Other IRR onlyRADB 664 99% 67
2804:7d88::/32 Valid Other IRR onlyRADB 626 98% 67

AS-SET

AS271567 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 8 are in fix.csv.

  • Route object: none3
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:7d88:8000::/34No route object for it. A route object for 2804:7d88:8000::/33 with origin AS271567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271567 in the RIR database for the space.627 of 636
Route object: none2804:7d88::/33No route object for it. A route object for 2804:7d88::/32 with origin AS271567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271567 in the RIR database for the space.626 of 636
Route object: none2804:7d88::/34No route object for it. A route object for 2804:7d88::/32 with origin AS271567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271567 in the RIR database for the space.626 of 636
Route object: RIR181.232.248.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR181.232.249.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR181.232.248.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:7d88::/32Route object only in RADB. Add it in the RIR database for the space.626 of 636

Route objects not announced

Route objects with origin AS271567 whose prefix no peer sees AS271567 announce. Many are kept on purpose (backup routes, space announced only in some places).

2804:7d88:8000::/33RADBValid

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.