bgpreport

Network · data from 2026-11-12

AS271117 Ultranet Ipava Telecom Ltda

Registry name: AS271117 - Ultranet Ipava Telecom Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271117, 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.

179.48.91.0/24 No ROA Other IRR onlyRADB 670 100% 66
179.48.90.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:7684:8000::/40 Valid Nonecovered by 2804:7684:8000::/34 635 100% 67
179.48.88.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
2804:7684::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:7684::/33 Valid Other IRR onlyTC 636 100% 67
2804:7684:8000::/33 Valid Other IRR onlyTC 636 100% 67
2804:7684::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:7684:4000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:7684:8000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:7684:c000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
179.48.88.0/24 Valid Other IRR onlyRADB, TC 200 30% 54
179.48.89.0/24 Valid Other IRR onlyRADB, TC 200 30% 54

AS-SET

PeeringDB's irr_as_set for AS271117: AS271117:AS-ULTRANET-IPAVA-TELECOM. 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 (AS271117 isn't in the set, or no route object for AS271117 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 objectsAS271117 in itNot covered
AS271117:AS-ULTRANET-IPAVA-TELECOM TC 1114 Yes 0

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: none2
  • Route object: none1
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none179.48.91.0/24No ROA covers it. Add a ROA for AS271117, maxLength 24.670 of 673
Route object: RIR179.48.91.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none179.48.90.0/24No ROA covers it. Add a ROA for AS271117, maxLength 24.667 of 673
Route object: RIR179.48.90.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: none2804:7684:8000::/40No route object for it. A route object for 2804:7684:8000::/34 with origin AS271117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271117 in the RIR database for the space.635 of 636
Route object: RIR179.48.88.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:7684::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:7684::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:7684:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:7684::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:7684:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:7684:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:7684:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR179.48.88.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR179.48.89.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673

Route objects not announced

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

179.48.88.0/22RADB, TCNo ROA
179.48.90.0/23RADBNo 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.