bgpreport

Network · data from 2026-11-12

AS271733 JRNET COMUNICACAO

Registry name: AS271733 - JRNET COMUNICACAO, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271733, 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:2884:4036::/47 No ROA None 1 0%low visibility 1
2804:8028::/40 Valid Nonecovered by 2804:8028::/34 636 100% 67
45.227.124.0/23 Valid Other IRR onlyTC 672 100% 66
45.227.126.0/24 Valid Other IRR onlyTC 671 100% 67
45.227.127.0/24 Valid Other IRR onlyTC 671 100% 67
2804:8028::/34 Valid Other IRR onlyTC 636 100% 67
2804:8028::/32 Valid Other IRR onlyTC 634 100% 67
2804:8028::/33 Valid Other IRR onlyTC 634 100% 67
2804:8028:4000::/34 Valid Other IRR onlyTC 632 99% 67
2804:8028:8000::/34 Valid Other IRR onlyTC 632 99% 67
2804:8028:c000::/34 Valid Other IRR onlyTC 632 99% 67
2804:8028:8000::/33 Valid Other IRR onlyTC 349 55% 64
45.227.125.0/24 Valid Other IRR onlyTC 201 30% 54
45.227.124.0/24 Valid Other IRR onlyTC 200 30% 54

AS-SET

PeeringDB's irr_as_set for AS271733: TC::AS271733:AS-ANNOUNCEMENTS. 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 (AS271733 isn't in the set, or no route object for AS271733 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.

NameDatabaseASNsSets Route objectsAS271733 in itNot covered
TC::AS271733:AS-ANNOUNCEMENTS TC 4237 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 17 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:2884:4036::/47No ROA covers it. Add a ROA for AS271733, maxLength 47.1 of 636
Route object: none2804:2884:4036::/47No route object for it. Add a route object with origin AS271733 in the RIR database for the space.1 of 636
Route object: none2804:8028::/40No route object for it. A route object for 2804:8028::/34 with origin AS271733 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271733 in the RIR database for the space.636 of 636
Route object: RIR45.227.124.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.227.126.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.227.127.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:8028::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:8028::/32Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:8028::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:8028:4000::/34Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8028:8000::/34Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8028:c000::/34Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8028:8000::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR45.227.125.0/24Route object only in TC. Add it in the RIR database for the space.201 of 673
Route object: RIR45.227.124.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673

Route objects not announced

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

45.227.124.0/22TCValid
45.227.126.0/23TCValid

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.